I'm for removing "String" and making it consistant with RFC2822.
Also my underatanding is that msg-id in the Received field is not
necessarily same as msg-id for the message itself and in fact is
basicly an id for particular SMTP connection i.e. envelope id
rather then being real message-id. As such gateway that speak
SMTP and put data in received should make sure that the ids they
put in are consistant with SMTP system and they should use some
other mechanism (X-field) if they want to preserve an id from
non-SMTP system.
On Thu, 22 Mar 2007, John C Klensin wrote:
In Section 4.4 on Trace Information, the "ID" clause of the Received field is
defined as
ID = CFWS "ID" FWS String / msg-id
This is claimed to be inconsistent with RFC 2822, which only permits msg-id.
"String" is there to provide additional flexibility for gateways, etc., for
which a message-ID format may not be appropriate, but it has been suggested
that we remove it in the interest of consistency.
Question: Is the production correct as is, or should "String" be eliminated
as a possibility?
Note that, if the answer is "ok as is", we may want to think about whether we
are happy with the syntax in in 2822.
john