Jeff Potter writes:
If a remote server sends Courier (0.45) what it claims is a uuencoded message, but the message includes non-uuencoded valid bits (e.g. ^M from a Mac); what does Courier do?
Hi All,
I should add a bit more detail, I realize. We've got a client who's getting email from someone else's server, where Courier is modifying an attachment "X-Mime-Autoconverted: from x-uuencode to 7bit by courier 0.45". The modified attachment can't be uudecoded on Windows or Unix (but can on OS X), it appears, because of '\r' characters.
"x-uuencode" is not valid MIME encoding.
What the heck is going on? I'm lost!
The obsolete software that generates "x-uuencode" nonsense should be upgraded or replace with something more modern, that properly implements MIME.
Setting "opt BOFHBADMIME=accept" might prevent this from happening. I'm not 100% sure. Besides, this would carry other side effects.
pgpteXjeaWML5.pgp
Description: PGP signature
