Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!triceratops.cis.ohio-state.edu!karl
From: karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste)
Newsgroups: comp.mail.headers
Subject: Re: Mail header wishlist
Summary: was Re: Another example why not to re-route
Message-ID: 
Date: 1 Dec 88 15:04:19 GMT
References: <1005@asylum.sf.ca.us>  <2696@sultra.UUCP> <1320@ksuvax1.cis.ksu.edu>
Sender: news@tut.cis.ohio-state.edu
Followup-To: comp.mail.headers
Organization: OSU
Lines: 13
In-reply-to: tar@ksuvax1.cis.ksu.edu's message of 1 Dec 88 09:24:13 GMT

tar@ksuvax1.cis.ksu.edu (Tim Ramsey) writes:
   The Options: header is a good idea.  How about a Bounced-By: header, to make
   it clear to mailing list repeaters that this mail shouldn't be broadcast to
   the list?  It could include the reason the mail was bounced.

That would be unnecessary if mailing lists would all make sure that,
when distributing out to the list's recipients, an Errors-To:
listname-request@listname-host-machine header were included.  Then
bounces would go to the admin only, and nowhere else.  Also, it helps
to have the From_ line indicate listname-request@listname-host-machine
to keep vacation(1) happily silent.

--Karl