J
Joe Quigley
Hello everyone,
I am having a problem with PDF attachments turning to Winmail.dat files for
certain external email recipients. Everything I have read states “Stop
sending rich text emails will solve your problemsâ€. I have told Outlook 2003
to only send emails as “Plain Text†but they still get winmail.dat files. The
recipients are not in our GAL and do not have local contacts so
Outlook/Exchange should not override the message format. It is not possible
to add these people to the GAL/Contacts as they are our clients which could
be anybody from around the world.
Packet captures of outbound transmissions show the normal handshake and
header information. It then sends this:
This is a multi-part message in MIME format.
------_=_NextPart_001_01C5C4FC.2799266D
Content-Type: text/plain;
..charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
At this time it sends the body of the message. After the body is complete,
it sends:
------_=_NextPart_001_01C5C4FC.2799266D
Content-Type: application/ms-tnef;
..name="winmail.dat"
Content-Transfer-Encoding: base64
And now the encoded attachment is sent.
As I understand it, ms-tnef is used to encode rich text messages. Why
outlook has chosen to use tnef for a plain text message? Is there any way to
force to stop encoding in tnef?? I know we can block delivery of rich text
messages on the Exchange server but that will affect everyone in the
organization which is something I would rather not do if at all possible.
Can anyone offer any thoughts or opinions on how to correct this??
I thank everyone who took the time to read this and to all who reply.
Regards,
Joe
I am having a problem with PDF attachments turning to Winmail.dat files for
certain external email recipients. Everything I have read states “Stop
sending rich text emails will solve your problemsâ€. I have told Outlook 2003
to only send emails as “Plain Text†but they still get winmail.dat files. The
recipients are not in our GAL and do not have local contacts so
Outlook/Exchange should not override the message format. It is not possible
to add these people to the GAL/Contacts as they are our clients which could
be anybody from around the world.
Packet captures of outbound transmissions show the normal handshake and
header information. It then sends this:
This is a multi-part message in MIME format.
------_=_NextPart_001_01C5C4FC.2799266D
Content-Type: text/plain;
..charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
At this time it sends the body of the message. After the body is complete,
it sends:
------_=_NextPart_001_01C5C4FC.2799266D
Content-Type: application/ms-tnef;
..name="winmail.dat"
Content-Transfer-Encoding: base64
And now the encoded attachment is sent.
As I understand it, ms-tnef is used to encode rich text messages. Why
outlook has chosen to use tnef for a plain text message? Is there any way to
force to stop encoding in tnef?? I know we can block delivery of rich text
messages on the Exchange server but that will affect everyone in the
organization which is something I would rather not do if at all possible.
Can anyone offer any thoughts or opinions on how to correct this??
I thank everyone who took the time to read this and to all who reply.
Regards,
Joe