atom feed21 messages in net.sourceforge.lists.courier-users[courier-users] To base64, or not to ...
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:[courier-users] To base64, or not to base64?
From:Jerry Amundson (jer@pbs.com)
Date:Jun 25, 2003 1:55:41 pm
List:net.sourceforge.lists.courier-users

How does Courier determine which Content-Transfer-Encoding when sending to a server which does not advertise 8BITMIME?

I send two PDF files to the same server. With the file encoded "quoted-printable", Adobe Reader opens it with "Wrong operand type", and most of the data does not display. With the file encoded "base64", Adobe Reader opens the file just fine and dandy.

Does not work..

--=_arsenic-26194-1056570429-0001-2 Content-Type: application/pdf; name="WASHDC.pdf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="WASHDC.pdf" X-Mime-Autoconverted: from quoted-printable to quoted-printable by courier 0.42.2

Does work..

--=_arsenic-26363-1056570509-0001-2 Content-Type: application/pdf; name="WINNMB.pdf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="WINNMB.pdf"

Thank you, jerry