[1582] in Moira
RE: some suggested mailhub.gen changes
daemon@ATHENA.MIT.EDU (Tom Coppeto)
Wed Jun 14 07:28:27 2000
From: "Tom Coppeto" <tom@MIT.EDU>
To: "Mark V. Silis" <mark@mit.edu>
Cc: <zacheiss@mit.edu>, <moiradev@mit.edu>, <postmaster@mit.edu>
Date: Wed, 14 Jun 2000 07:44:47 -0400
Message-ID: <NDBBKHCHPJDKBDPHJLDAAEEODAAA.tom@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200006140446.AAA05512@chicago.mit.edu>
It sounds like:
1. we can go ahead with this moira patch
2. moira should prevent creation or renaming of owner-lists
3. existing owner-lists that were not automatically generated need to be
identified and changed
4. when the above 3 are complete, we can go ahead with a normal sendmail
does this sum it up? 1 & 2 are in garry's court. who will volunteer to do 3?
- Tom
-----Original Message-----
From: Mark V. Silis [mailto:mark@MIT.EDU]
Sent: Wednesday, June 14, 2000 12:47 AM
To: tom@MIT.EDU; mark@MIT.EDU
Cc: zacheiss@MIT.EDU; moiradev@MIT.EDU; postmaster@MIT.EDU
Subject: Re: some suggested mailhub.gen changes
I went ahead and did some testing with this configuration, having
my mit.edu MX record pointed at the test mailer with the non-pathched
sendmail,
and garry's new aliases file. This does in fact correct the problem. Here's
why: When you send to a list that has a fully expanded owner list, sendmail
doesn't do a look up on the list and end up setting the return-path to the
same thing again. What it actually ends up setting it to is <> since
owner-<listname> has no owner, and that ends any possible mailing loop.
Here is an example, network is a self owned list with an entry for which
the mailers cannot deliver. Someone sends mail to network, mail bounces to
the Return-Path: <owner-network@mit.edu>, which of course will bounce again
since that list is simply comprised of the members of network, but this
time we have Return-Path: <> which can never loop back! As long as the
Return-Path is always set to owner-<listname> and not simply the expansion
of
owner-<listname> ie (owner-network vs. network) looping bugs will be
avoided.
And garry's patch does in fact enforce this behaviour by setting
owner-<listname> to be a full expansion of the list membership.
So I would say as long as we can prevent people from creating
owner-<listname>
lists, and maybe cleanup the ones out there there to be sure, that this is a
safe solution.
-- Mark
