> The Message-ID: header was not RFC-compliant.
Message-Id: <[EMAIL PROTECTED]>
ABNF extracted from RFC 2822 Internet Message Format:
Actually, RFC822 is still the official standard (per http://www.rfc-editor.org/rfcxx00.html). RFC822 has:
msg-id = "<" addr-spec ">" ; Unique message id
addr-spec = local-part "@" domain ; global address
domain = sub-domain *("." sub-domain)
sub-domain = domain-ref / domain-literalThat means that "81.255.84.73" must either be a domain-ref or domain-literal. Domain-ref and domain-literal are covered by RFC822 section 6.2.3, which make it pretty clear that the "81.255.84.73" above is a domain-ref (since it has no brackets), and 81.255.84.73 is clearly not a valid hostname.
So the only argument would be whether or not RFC2822 should supersede RFC822. Even if people felt that it should (which is, like all things RFC, subject to interpretation!), programs generating headers are expected to follow the RFCs strictly and programs interpreting headers are expected to follow the RFCs loosely (except, of course, for a programs designed to analyze headers looking for technical violations of the RFCs).
-Scott
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
