🚀 go-pugleaf

In article <jstewart.711310628@cunews>, 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.  The only 
|> solution seemed to be to check the comments in header lines for tokens
|> like "list" or "distribution" that are generally found in messages from
|> a LISTSERV.  I'd be a lot happier though if LISTSERV would add an
|> Errors-To: header to provide a proper place to report delivery problems to.
|> 
|> I'd guess that LISTSERV also has some klugey logic to try to distinguish
|> a bounce reply from a list submission.  

LISTSERV catches bounces (1) if "Undeliver" is in the Subject: (2) if the
sender is one of a set of typical error senders such as "mailer-daemon",
"postmaster", "root". Yes, kludgey.

An Errors-To: header is the right way to go; I can't say why it hasn't been
done.

Where is the right followup for this? I removed n.s.readers from this one.

--Shane