atom feed21 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: To base64, or...
FromSent OnAttachments
Jerry AmundsonJun 25, 2003 1:55 pm 
Sam VarshavchikJun 25, 2003 3:09 pm 
Jerry AmundsonJun 26, 2003 9:04 pm 
Jerry AmundsonJun 26, 2003 9:25 pm 
Sam VarshavchikJun 27, 2003 7:42 am 
Sam VarshavchikJun 27, 2003 7:58 am 
Jerry AmundsonJun 27, 2003 8:38 am 
Sam VarshavchikJun 27, 2003 9:41 am 
Jerry AmundsonJun 27, 2003 2:55 pm 
Sam VarshavchikJun 27, 2003 6:35 pm 
Jason HaarJun 29, 2003 4:54 pm 
Jerry AmundsonJul 2, 2003 12:25 pm 
Sam VarshavchikJul 2, 2003 3:10 pm 
Jerry AmundsonJul 2, 2003 9:55 pm 
Sam VarshavchikJul 2, 2003 11:26 pm 
Jerry AmundsonJul 3, 2003 7:10 am 
Sam VarshavchikJul 3, 2003 8:37 am 
Jerry AmundsonJul 3, 2003 10:24 am 
Sam VarshavchikJul 3, 2003 6:07 pm 
Systems AdministratorJul 3, 2003 11:08 pm 
Jerry AmundsonJul 4, 2003 1:23 am 
Subject:Re: [courier-users] Re: To base64, or not to base64?
From:Jason Haar (Jaso@trimble.co.nz)
Date:Jun 29, 2003 4:54:40 pm
List:net.sourceforge.lists.courier-users

This bug has nothing to do with Courier. I've seen it myself over the past two years - Qmail to Exchange environment.

The problem is that the *client* is sending a BINARY attachment (PDF) and it's Q-P'ing it instead of base64'ing it.

I don't know if the client does Q-P incorrectly - but that was the problem. I found that the resulting PDF couldn't be viewed under *any* Unix mailer (i.e. the PDF was corrupt), but if it was forwarded through to an Exchange server, Outlook could read it fine, and if you IMAP'ed into Exchange, a Unix mailer could now read it (IMAP showed it as base64 BTW).

I'd guess it's something to do with line delimiters and how Winblows does it with Q-P vs how it should have been done.

-- Cheers

Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1