[Top] [All Lists]

Re: Restrictions on the Content-Type "message"

1999-01-04 13:10:21
At 09:57 AM 1/4/99 -0800, Ned Freed wrote:
This would be a valid point if message/rfc822 were strictly aligned with
RFC822. But it isn't -- the name, which was chosen and implemented long
before the exact rules for the type were put in place, is misleading.

Message/rfc822 was specifically designed to allow for material that isn't
legal according to RFC822 (and, I suspect, DRUMS). Specifically, the
requirements for what headers have to be present are substantially relaxed,
as are the syntax rules.

I think this suggests a legitimate question about some sort of labeling
which notes that the content really is (honest to goodness) conformant
specifically with 822, or with netnews, or whatever.  (822 variants, such
as an incomplete draft message, versus a fully 'received' one are useful
distinctions, too.)


Dave Crocker                                       Tel: +60 (19) 3299 445
<mailto:dcrocker(_at_)brandenburg(_dot_)com>             Post Office Box 296, 
                                         Serdang, Selangor 43400 MALAYSIA
Brandenburg Consulting                                          
<>                       Tel: +1 (408) 246 8253
Fax: +1(408)273 6464              675 Spruce Dr., Sunnyvale, CA 94086 USA