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: <8402240735.AA16931@ucbopal.CC.Berkeley.ARPA> Date: Thu, 1-Mar-84 02:35:49 EST Article-I.D.: hou3c.327 Posted: Thu Mar 1 02:35:49 1984 Date-Received: Tue, 28-Feb-84 00:26:32 EST Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 183 To: header-people@mit-mc Since D.Brown has dropped by name into the pot, I guess it is time to dust off my "Basic Message Format" again. The "Currently-to" concept is the about the same as the "Relay-to" header field in my basic message format. I prefer "Relay-to" since it is already defined for military messages. For those that have not kept a copy of my basic message format header fields, here is a summary of the header fields. The "envelope information" is contained in the postal heading. ----- Basic Message Format - 2 - "Heading Components" Version 3 - 23 Feb 84 1. Basic Message Structure: Parts: Sub-parts: HEADING Transmission Heading Batch Heading Postal Heading Message Heading TEXT Message Text (Body of Message) ENDING Message Ending Postal Ending Batch Ending Transmission Ending The Internet text message format as defined by the "Standard for the Format of ARPA Internet Text Messages" (RFC 822) has a heading and a text. No ending is defined. Basic message format classifies header fields into two groups, Message Heading and Postal Heading fields. In addition to RFC 822 header fields there are additional header for use in the Postal Heading. No attempt has been made to define "Batch" or "Transmission" fields since these are more the concern of the network and the transport system being used. "Classification", "Precedence" and "Resent-Precedence" have been added to the Message Heading to permit user definition of these fields. 2. Basic Message Format Header Fields by Sub-Part and Component. POSTAL HEADING 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: _____________________________________________________ MESSAGE HEADING SUB-PART COMPONENT FIELD _____________________________________________________ Readdressal Date-Time Resent-Date: Message Heading(s) Originator's Resent-From: Address Resent-Sender: Resent-Reply-To: Originator's Resent-Message-ID: Message ID. Precedence Resent-Precedence: Receiver's Resent-To: Address Resent-cc: Resent-bcc: Resent-Exempt: _____________________________________________________ Original Date-Time Date: Message Heading Originator's From: Address Sender: Reply-To: Originator's Message-ID: Message ID. Precedence Precedence: Receiver's To: Address cc: bcc: Exempt: Security Classification: Classification Content Subject: Information Keywords: In-Reply-To: References: Encryption Encrypted: Field _____________________________________________________ Heading Comments Comments: Comments Field _____________________________________________________ Notes: (a) Fields not defined in RFC 822 are: Posted-Date, Posted-From, Post-ID, Postmaster, Relay-To, Do-Not-Relay-To, Resent-Precedence, Precedence, Resent-Exempt, Exempt, Classification. The order of sub- parts differs from RFC 822 Article 4.1 in that "source" is defined as: source = [trace] [resent] originator (b) Each sub-part of the heading begins with its corresponding date- time field. Fields pertaining to one sub-part may not be placed in another sub-part. With the exception of the date-time field which begins the sub-part, the order of fields within the sub-part is not defined. However the above order is recommended. (c) There may be none, one or more "readdressal message heading" sub- parts in the message heading. If there is more than one "readdressal message heading" the later ones precede the earlier ones. (d) "Relay-To" fields may be deleted by relaying hosts (Mail Transport Agent programs) when delivery has been made (or protected) by that host (MTA). (e) Relaying hosts (MTA's) will not make changes to the Message Heading within an mail system using basic message format. Gateways to non-basic message format mail systems, may translate header fields into other formats. However, if the other mail system's format is incompatible with the basic message format, the message should be quoted in the text of the other systems message. The same applies to incompatible messages being entered into an a basic message format mail system. (f) There may be only one "Date:", "From:", "Sender:" and "Message- ID:" field per original message. Relaying hosts may not add or change the "Message-ID" field. (g) "Exempt" and "Resent-Exempt" fields are optional user fields that may be used with collective addresses to indicate that the drafter (or user resending the message) does not want the message sent to one or more addressees in the collective address. Syntax is same as "To": exempt = "Exempt" ":" 1#address resent-exempt = "Resent-Exempt" ":" 1#address ----- Comments? Bill Wells, RMC, USNR-R wcwells@BERKELEY.ARPA ucbvax!wcwells Computing Services, 297 Evans Hall, University of California, Berkeley CA 94720