🚀 go-pugleaf

In article <MeNRg8y00WBwE6dt42@andrew.cmu.edu> John Gardiner Myers <jgm+@CMU.EDU> writes:
>jstewart@alfred.carleton.ca (John Stewart) writes:
>> I certainly feel abused by this practise.  I had to write a script to bounce
>> undeliverable mail (account disk space full, no mail folder, etc.) on our
>> mailframe.  Messages from a LISTSERV can't be handled in the same way as
>> regular mail because the Reply-To: header line points back to the list -- 
>> bouncing the message to that address causes a mail loop.
>
>You shouldn't be bouncing mail to "Reply-To:".  You should bounce it
>to the envelope return address, as specified in section 5.3.3. of RFC
>1123.  Many mailers put the envelope return address in the
>"Return-Path:" header.

I always thaught it was the Sender: header in bitnetland that error
reports got bounced to.  Of cource listserv puts the name of the list in
here also with the intent of makeing the bounces go back to the list
where it thinks it can filter them out.  I know for sure the Reply-to is
the wrong place.  When it is set to the author of the article it makes
no sence at all when the article was sent to a list as the author of the
article does not have any use for 30 bounced mail messages telling him
that the list maintainer has no idea (or does not care) that addresses
in the mailing list do not work.  Many sites bounce mail to the From:
and that screws up most listserv lists by sending reams of junk back to
the poor poster that should have gone to the list maintainer.
-- 
Chad Adams              __               Educational Computing Network
Systems Programmer     /  ) /         /  University Park, IL  USA
1-708-534-0200        /    /_  __, __/   ECN, networking in IL since 1975
c-adams@bgu.edu      (__/ / /_/_/_(_/_   "Wherever you go, there we are."