Every now and then, I get these when apache on our server, or another server, sends out an email (mainly monitor emails, or other site specific generated emails from php).

The only difference in these, compared to ones that come through ok, is the existence of at least one character. Something like a , or a ü. Of course, that there is going to make courier hate this email... Heh.

I know of a setting, which tells courier to ignore BOFHBADMIME... And sends the email through... But that is more of a band aide. What I am trying to find, is what header, or portion of the email is courier expecting to find, to accept a plain text email with a 'funny char' in it?

The notice: +++ CORRUPTED MESSAGE This is the Courier Mail Server 0.50 on gg.

I received the following message for delivery to your address. This message contains several internal formatting errors. This is often caused by viruses that attempt to infect remote systems. Instead of blocking this message, I converted it to a safe, text-only attachment that can be safely read with a text editor.

This sometimes also happens when the sender's mail software has a bug that creates improperly-formatted messages. Although these kinds of formatting errors may often be ignored by other mail servers, this server detects and intercepts improperly-coded messages in order to prevent viruses from taking advantage of bugs in E-mail programs:

---------------------------------------------------------------------------- This message contains improperly-formatted binary content, or attachment.

See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> for more information.

That URL... Blah blah blah blah... Whats important in that long winded technical document in regards to what I'm looking for? I'm not interested in every encoding method on the planet to understand every character set in the world... I just want to find out what needs to be set, to make courier like plain text emails from php that may or may not contain a MacOS Option-Key inserted character?