ietf-dkim
[Top] [All Lists]

Re: [ietf-dkim] Optional sender

2008-02-03 19:59:01


Frank Ellermann wrote:
Hector Santos wrote:

Per x822, Sender: is OPTIONAL and not a network required
control header. It is more information than anything else.

We are not reading the same copy of 2822upd.

You're right. We are talking about the current standards, 822 and 2822, which ever you wish to follow.

PER RFC 822, the Minimum Requirement is:

     A.3.  COMPLETE HEADERS

     A.3.1.  Minimum required

     Date:     26 Aug 76 1429 EDT        Date:     26 Aug 76 1429 EDT
     From:     Jones(_at_)Registry(_dot_)Org   or   From:     
Jones(_at_)Registry(_dot_)Org
     Bcc:                                To:       Smith(_at_)Registry(_dot_)Org

        Note that the "Bcc" field may be empty, while the  "To"  field
        is required to have at least one address.

If a system is running in legacy mode, that you are incorrect to state it is a required. Are you ready to state that legacy systems do not exist or even modern systems who for some reason or another choose to run in legacy mode?

PER RFC 2822,

    The only required header fields are the origination date field and
    the originator address field(s).

Per section 3.6.2 SENDER SHOULD only be used when the FROM is not the actual transmitter of the message. It is stated very clear:

   If the originator of the message can be indicated
   by a single mailbox and the author and transmitter are identical, the
   "Sender:" field SHOULD NOT be used.  Otherwise, both fields SHOULD
   appear.

Therefore, as I said, it is not a REQUIRED field and only useful when the AUTHOR is not the actual transmitter.

For you to state it is a requirement in ALL cases and therefore implying it is a fundamentally essential for email operations, well, you know perfectly well it is not true.

--
Sincerely

Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com

_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html