ietf-smtp
[Top] [All Lists]

Re: Last Call: draft-klensin-rfc2821bis [...]

2008-01-24 03:08:35

On Thursday 24 January 2008 09:55:41 Alessandro Vesely wrote:
Assuming that SMTP doesn't need to delve into boundaries and complex
network topologies, the best it can do is to refer to current best
practices. E.g, like so:
    To expand an alias, the recipient mailer replaces the recipient
    address in the envelope with each of the expanded addresses in
    turn. Trace information SHOULD be removed and the envelope sender
    address SHOULD be changed according to local forwarding policies,
    or left intact in case of lack thereof.

If by 'Trace information' you mean a Return-Path, that is fine,
but the text needs to say so. The 'Trace information' also covers
the Received header fields, which must not be deleted!


Secton 4.4. of the draft currently say:

   An Internet mail program MUST NOT change a Received: line that was
   previously added to the message header section.  SMTP servers MUST
   prepend Received lines to messages; they MUST NOT change the order of
   existing lines or insert Received lines in any other location.

it might be prudent to be say:
  MUST NOT change --> MUST NOT change or delete


Mark

<Prev in Thread] Current Thread [Next in Thread>