|
From: Paulo M. <pj...@fc...> - 2003-01-22 14:51:02
|
Hi all! I'm using and helping with development of NOCC webmail=20 (nocc.sourceforge.net).=20 Recently appeared a bug report that NOCC was "Unable to send messages wit= h=20 SpamAssassin installed". When the user try to send a message each mail=20 gets caught with the message: "Disallowed MIME characters found in headers"! Lookin at your FAQ (at the bootom of the there's an excerpt from=20 http://qmail-scanner.sourceforge.net/FAQ.php), I can't get where is the=20 problem. Either that or I don't know how to read RFCs (as the SPAMers :). Looking at RFC822, all lines are separeted with CRLF OS-independent, so=20 the message is sent with CRLF to the MTA. After that, it should handle it= =20 properly and deliver it to its destination. Please give me some hints to solve the problem. Or even an mail address=20 where I can sent a message with NOCC and you could get it raw. Thanks in advance. Best regards, --=20 Paulo Matos ----------------------------------- ---------------------------------- |Sys & Net Admin | Servi=E7o de Inform=E1tica = | |Faculdade de Ci=EAncias e Tecnologia | Tel: +351-21-2948596 = | |Universidade Nova de Lisboa | Fax: +351-21-2948548 | |P-2829-516 Caparica | e-Mail: pj...@fc... | ----------------------------------- ---------------------------------- --- excerpt starts here --- 15. Hey! what's this "Disallowed MIME characters found in headers" doing=20 to <product X> messages!!!.=20 That internal function in Qmail-Scanner blocks any MIME e-mail message=20 that contains either NULL characters ("\0") or CR chars ("\r") in the=20 headers. Such characters are used by viruses/trojans to bypass antivirus=20 scanners, and the presence of this feature automatically blocks them.=20 It also has the side effect of blocking quite a bit of SPAM - as most=20 spammers hand-code their SPAM generators and don't know how to read RFCs.= =20 Unfortunately, some "good" e-mail generators are also broken/misconfigure= d=20 and trigger the quarantine action. Typically what has happened is that a=20 config file for the generator has been edited from within Windows [Unix=20 uses LF "\n" to delimit end of lines, whereas Windows uses "CRLF "\r\n"],= =20 and of course, it's thrown CR chars into what should have been text-only=20 config details. Only the "owner" of the particular e-mail generator can=20 fix this problem. Qmail-Scanner is doing it's job.=20 --- excerpt ends here --- |