In an old message from 2006, Jason Haar wrote >If you searched qmail-scanner-queue.pl, you'd see that "Disallowed MIME >Content" only shows up once. It means someone sent a mail message that:.. > >a> claims to be MIME (by the presence of a "MIME-Version" header) >b> has a "Content-Type" header that is NOT in the RFC-prescribed format >of "XXX/YYY" (e.g. "text/plain") > >As such Qmail-Scanner tags it as broken and quarantines it. > >Sounds like a broken mailer in action to me...
See http://www.mail-archive.com/qmail-scanner-general@lists.sourceforge.net/msg06796.html By doing a bit more research, it turns out that this appears to be incorrect. According to RFC 2045, section 5.2, it looks as though the ascii should be assumed, even with no Content-Type or a broken Content-Type header. >5.2. Content-Type Defaults > > Default RFC 822 messages without a MIME Content-Type header are taken > by this protocol to be plain text in the US-ASCII character set, > which can be explicitly specified as: > > Content-type: text/plain; charset=us-ascii > > This default is assumed if no Content-Type header field is specified. > It is also recommend that this default be assumed when a > syntactically invalid Content-Type header field is encountered. In > the presence of a MIME-Version header field and the absence of any > Content-Type header field, a receiving User Agent can also assume > that plain US-ASCII text was the sender's intent. Plain US-ASCII > text may still be assumed in the absence of a MIME-Version or the > presence of an syntactically invalid Content-Type header field, but > the sender's intent might have been otherwise. ------------------------------------------------------------------------------ _______________________________________________ Qmail-scanner-general mailing list Qmail-scanner-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
