Re: egcs-announce mailing list

[Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>]

At 09:29 30.11.98 , Jeffrey A Law wrote:
>
>  In message
<Pine.GSO.4.05.9811291628260.16972-100000@alphard.dbai.tuwien.ac.a
>t>you write:
>  > On Sat, 28 Nov 1998, Jeffrey A Law wrote:
>  > > The egcs-announce list now lives on the egcs machine
>  > > (egcs-announce@egcs.cygnus.com).
>  > 
>  > I noticed the following headers, for I had to update my procmail recipes
>  > due to this change:
>  >   
>  >   Mailing-List: contact egcs-announce-help@egcs.cygnus.com; run by ezmlm
>  >   X-No-Archive: yes
>  >   Delivered-To: mailing list egcs-announce@egcs.cygnus.com
>  > 
>  > Why the X-No-Archive: yes?
>  > 
>  > Is there any specific reason to abandon the Sender: header in favor of
>  > the the Mailing-List: and Delivered-To: headers? (Actually I believe that
>  > these are not RFC compliant, though I haven't check this yet.)
>Because that's what qmail+ezmlm does by default.  We've changed both the
>MTA and the list server.

There's absolutely no problem with these headers, they are under full
application control and I don't think they have to conform to any RFC
(except the "headername: headertext" convention) and they are used by qmail
and ezmlm to prevent mail loops.
In fact, if you ever peek into the qmail mailing list and read the postings
from the qmail+ezmlm author D.J.Bernstein, you'll know that this guy is the
last one to violate standards :-).

On the filtering issue it might be a good idea to add "Sender:
owner-egcs-cvs" (or whatever was written there before, that is what I was
filtering on and I think thats enough) to the file headeradd in the ezemlm
mailing list config dir. This will help backwards compatibility and that's
probably exactly one of the things Jeff wanted to shake out before the big
lists are converted.

I'm already amazed by the new speed of egcs-cvs, typical delivery time is
down to seconds from ~30-50min, and that was one of the fastest lists at
cygnus.

Congratulations!

Franz.