At 09:50 AM 1/22/2003, Paulo Matos wrote:
As the FAQ you read says, the error "Disallowed MIME characters found in headers" occurs when a \r or \0 appears in a header line. I just read the source to confirm this, and it appears to be correct. Header lines are separated at CRLFs or LFs, due to using Perl's "while (<STDIN>)" construct. Keep in mind that this error is caused by qmail-scanner itself, not Spamassassin (as your bug-reporter indicated).I'm using and helping with development of NOCC webmail (nocc.sourceforge.net).Recently appeared a bug report that NOCC was "Unable to send messages with SpamAssassin installed". When the user try to send a message each mail 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 http://qmail-scanner.sourceforge.net/FAQ.php), I can't get where is the 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 the message is sent with CRLF to the MTA. After that, it should handle it properly and deliver it to its destination. Please give me some hints to solve the problem. Or even an mail address where I can sent a message with NOCC and you could get it raw.
Ted Behling, Chief Penguin Surgeon
Monarch Information Systems, Inc.
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
