Mail header wishlist (was Re: Another example why not to re-route)

Article View: comp.mail.headers

Article #627

#627

From: Tim Ramsey
Date: Thu, 01 Dec 1988 09:24

12 lines
1114 bytes

[ I've added comp.mail.headers and directed followups there since this thread
  seems to be moving in that direction.  -- Tim]

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.

-- 
Timothy Ramsey, USENET Keeper-Upper
BITNET: tar@KSUVAX1
Internet: tar@ksuvax1.cis.ksu.edu
UUCP: ...!rutgers!ksuvax1!tar -or- ...!{pyramid,ucsd}!ncr-sd!ncrwic!ksuvax1!tar

Technical Details

Message-ID: <1320@ksuvax1.cis.ksu.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!att!rutgers!deimos!ksuvax1!tar

References: <1005@asylum.sf.ca.us> <VIXIE.88Nov29011054@bacchus.pa.dec.com> <2696@sultra.UUCP>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!att!rutgers!deimos!ksuvax1!tar
From: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Newsgroups: comp.mail.headers,comp.mail.uucp,comp.mail.misc
Subject: Mail header wishlist (was Re: Another example why not to re-route)
Message-ID: <1320@ksuvax1.cis.ksu.edu>
Date: 1 Dec 88 09:24:13 GMT
References: <1005@asylum.sf.ca.us> <VIXIE.88Nov29011054@bacchus.pa.dec.com> <2696@sultra.UUCP>
Reply-To: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Followup-To: comp.mail.headers
Organization: Kansas State University, Dept of Computing & Information Sciences
Lines: 12

Reply to Parent Message