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 ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
