Re: [Qmail-scanner-general]Disallowed characters found in MIME headers

2004-05-15 Thread Don Walters
Based on the differences between the 2, I would suspect a problem with the way his software is generating the MIME boundary tag. Ask him if he can define in the program script or code to use a different boundary definition such as: Content-Type: multipart/mixed; boundary="--=NextPart" Thi

Re: [Qmail-scanner-general]Disallowed characters found in MIME headers

2004-05-15 Thread Doug Monroe
Don Walters wrote: I was mainly wondering if you can identify (easily) what email headers are ugly that QS doesn't like. This way, I can point to the specific problem that the other admin needs to fix in order for these messages to be sent with clean mime. debug log tell you anything? Do you s

Re: [Qmail-scanner-general]Disallowed characters found in MIME headers

2004-05-15 Thread Bob Jones
Don Walters wrote: Content-Type: multipart/mixed; boundary="-" This is a MIME encoded message from FutureLynx. Decode it with "munpack" or any other MIME reading software. Mpack/munpack is available via anonymous FTP in ftp.andrew.cmu.edu:pub/mpack/ --- Enclosed is a message that you requested

Re: [Qmail-scanner-general]Disallowed characters found in MIME headers

2004-05-15 Thread Don Walters
just curious - has the sender tried sending it to you from a different mail-clinet (even yahoo)?? It may just be how the mail cleint formats that MIME..I know that has been an issue with Outlook Express and some attchments that we received Well, this is how it was explained to me... there is some

[Qmail-scanner-general]Disallowed characters found in MIME headers

2004-05-15 Thread Don Walters
I'm getting some legitimate mail that is being blocked by qmail-scanner. I know I can turn off MIME checks by setting $BAD_MIME_CHECKS='0' and the messages are allowed to come through just fine. The admin for the sending mail server has agreed to speak with me about this, and I'd like to give