Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!wcwells%ucbopal.CC@Berkeley.ARPA From: wcwells%ucbopal.CC@Berkeley.ARPA (William C. Wells) Newsgroups: net.mail.headers Subject: Re: envelope information Message-ID: <8402250229.AA27344@ucbopal.CC.Berkeley.ARPA> Date: Fri, 24-Feb-84 21:29:18 EST Article-I.D.: hou3c.330 Posted: Fri Feb 24 21:29:18 1984 Date-Received: Tue, 28-Feb-84 00:30:00 EST Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 72 To: header-people@mit-mc.ARPA Envelope Information - 1.1 correction Oh joy. My last message: Date: Fri, 24 Feb 84 11:30:26 pst From: wcwells@ucbopal (William C. Wells) Message-Id: <8402241930.AA20770@ucbopal.CC.Berkeley.ARPA> Subject: Re: envelope information was truncated when it was transmitted locally. Here is the bottom part again. Sorry for the repeat. ---- SUB-PART COMPONENT FIELD _____________________________________________________ Postal Postmark Posted-Date: Heading Posted-From: Post-ID: Postmaster: Return Field Return-Path: Relay Instructions Relay-To: Do-Not-Relay-To: Trace Fields Received: _____________________________________________________ The "Postmark" fields serve to identify each message transmission. --- My assumption is that a unique message identified by "Date" "From" and "Message-ID" (fields added by the user agent mail formatting/generation program) might be retransmitted to one or more addresses of the original message (for example, when the original message was returned to sender due to a host being down). The "Postmaster" field serves to identify the Postmaster of the of the originating mail transport agent. This is needed where one mail transport agent is serving several hosts, workstations and microcomputers. (This should handle the case where the originator of a message is not in the same mail domain as the Postmaster of the originating mail transport agent.) "Return-path" - same as RFC 822, with one note: In addition to the last mail transport agent adding(/modifying?) this field, I think "gateway" mail transport agents should also add/modify this field. The "Relay-to" field tells the receiving mail transport agent that he(/she?) is responsible only for forwarding the message to a specific list of addressee (not all addressee in the message heading). It takes precedence over addresses in the message heading. It may be used by either the mail transport agent or the user agent. One example of user agent use would be in the retransmission of a message which was returned to the sender, and the sender does not want to retransmit to all addressees but only to the addressee that did not get the message. The "Do-not-relay-to" field is intended to be used with collective addresses where mail transport agent has or is making delivery to specific member(s) of the collective address via other means (for example via an alternate mail system). This assumes the mail transport agent applying this field knows the composition of the collective address. "header-people@mit-mc.ARPA" is an example of a collective addresss. "Received" - same as RFC 822. Bill Wells, U.C. Berkeley wcwells@Berkeley.ARPA or ucbvax!wcwells