It has been suggested that some legal but unused RFC 2822 Message-ID's
will break a significant amount of deployed news infrastructure. If, in
fact, we're not able to find any existing software that generates such
"dangerous" Message-IDs, what would ietf-822 folks think about
tightening the legal-to-generate Message-ID definition when RFC 2822
moves to draft standard? This would encourage the trend toward using
RFC 2822 as a universal Internet Messaging Format document, which can be
used across mail and news.
Could someone suggest the RFC 2822 syntax that would be compliant with
RFC 1036 and established practice (i.e., shorter than 250 characters and
doesn't include backslash-escaped space or control characters)? Could
other people check their archives of messages to see how many extant
Message-IDs are legal under RFC 2822 Section 3 syntax but violate news
syntax?
- dan
--
Dan Kohn <mailto:dan(_at_)dankohn(_dot_)com>
<http://www.dankohn.com/> <tel:+1-650-327-2600>