< hansen(_at_)pegasus(_dot_)att(_dot_)com writes:
<< If you receive a mail message that contains a Content-Type: header, and
<< you want to treat it as a MIME message, the ONLY way to start is to look
<< for the Mime-Version: header.
<
< That is hardly the case.
<
< RFC 1049 Content-Type values do not match the syntax of MIME Content-Type
< values. If you treat non-MIME-parseable content-types as "text/plain;
< charset=us-ascii", or if you treat them per RFC 1049 et al., your mail
< reader will not break.
RFC 1049 is not the only other place which has defined content-type headers.
<< If your mail reader doesn't check for at least the presence of the
<< Mime-Version: header, then you can expect it to break once in a while
<< when one of these messags crosses your system.
<
< None of my MIME parsers look at MIME-Version. They don't break on such
< messages--such messages get handled as "text/plain; charset=us-ascii".
They will certainly sure break on messages which contain non-ascii
characters, whether it be binary or just non-ASCII text.
Tony Hansen
hansen(_at_)pegasus(_dot_)att(_dot_)com,
tony(_at_)attmail(_dot_)com
att!pegasus!hansen, attmail!tony