How does Courier determine which Content-Transfer-Encoding when sending to a server which does not advertise 8BITMIME?
It always uses quoted printable.
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.
To the best of my knowledge, Adobe Reader is not a mail client. It's an external application that, supposedly, set up as a handler for the application/pdf MIME type, in the mail client.
The mail client, in theory, is responsible for decoding the attachment, and then invoking the configured handler.
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
Something else is broken here. If the original message contained 8-bit content, it is illegal for that to have quoted-printable transfer encoding.
I suspect that something horribly broken is generating 8-bit crap; marks it as 7-bit quoted printable; Courier sees that the MIME section contains 8-bit data, and converts 8-bit crap to quoted-printable crap. The final result is the same crap.
pgp00000.pgp
Description: PGP signature
