I am sending a MIME email message including html text and an attachment (PDF
file) using microsoft outlook. Outlook is encoding the pdf attachment
correctly as follows:
------=_NextPart_000_0064_01C11FFF.7518DDD0
Content-Type: application/pdf;
name="MemberMailing2001-07-26.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="MemberMailing2001-07-26.pdf"
JVBERi0xLjMNJeLjz9MNCjQwNiAwIG9iag08PCANL0xpbmVhcml6ZWQgMSANL08gNDA5IA0vSCBb
IDE0NTMgODA3IF0gDS9MIDMxMjY5NyANL0UgMTI5MTM5IA0vTiAyMSANL1QgMzA0NDU4IA0+PiAN
ZW5kb2JqDSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB4cmVmDTQwNiA0MSANMDAwMDAwMDAxNiAwMDAwMCBuDQowMDAwMDAxMTg5IDAwMDAwIG4NCjAw
<snip>
The recipient is finding that this attachment is being received in a
quoted-printable format, obviously converted by a mail gateway at some
point. It seems to me that this base64 attachment has been re-encoded as
quoted-printable for some reason. It appears as:
------=_NextPart_000_0064_01C11FFF.7518DDD0
Content-Type: application/pdf;
name="MemberMailing2001-07-26.pdf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="MemberMailing2001-07-26.pdf"
JVBERi0xLjMNJeLjz9MNCjQwNiAwIG9iag08PCANL0xpbmVhcml6ZWQgMSANL08gNDA5IA0vS=
CBb
IDE0NTMgODA3IF0gDS9MIDMxMjY5NyANL0UgMTI5MTM5IA0vTiAyMSANL1QgMzA0NDU4IA0+P=
iAN
<snip>
Can someone explain why a gateway would perform this type of conversion? The
recipient is obviously having problems reading this attachment.
Thanks
Keith
Is there
mime-version: 1.0
in your main headers?
--
Darren New / Senior MTS & Free Radical / Invisible Worlds Inc.
San Diego, CA, USA (PST). Cryptokeys on demand. dn...@san.rr.com
"You probably noticed you can't breath underwater. Hence the tank."
-- PADI instruction manual, page 107.
Yes, the MIME version header is there. It would seem that only selective
gateways are performing this mapping.
Keith
"Darren New" <dn...@san.rr.com> wrote in message
news:3B71AE7D...@san.rr.com...
Keith> Yes, the MIME version header is there. It would seem that only
Keith> selective gateways are performing this mapping.
The gateway could be broken, in treating your base64 as 8bit when
re-encoding, but as a workaround, you could try shortening your lines
by a couple of characters. I'm guessing that it's triggered by lines
over 76 characters and is (mistakenly, I think) counting the CR and LF
as part of the line.