5 messages in net.sourceforge.lists.courier-users[courier-users] Re: x-uuencode to 7bi...
FromSent OnAttachments
Jeff PotterFeb 23, 2005 9:44 am 
Jeff PotterFeb 23, 2005 9:56 am 
Sam VarshavchikFeb 23, 2005 3:47 pm 
Jeff PotterFeb 24, 2005 6:46 am 
Sam VarshavchikFeb 25, 2005 3:39 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: x-uuencode to 7bit questionActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Feb 23, 2005 3:47:34 pm
List:net.sourceforge.lists.courier-users

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.