Attachments visible to Outlook users, not to Outlook Express users

[Philip Herlihy]

Attachments sent by just one of our users from Outlook 2003 (fully
updated) cannot be read by another user in Outlook Express. She can
receive attachments from other users (this isn't the security issue
where OE is hiding attachments that might represent a security risk).

Looking at the message source in OE I see this:

Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="winmail.dat"

I understood it's well-known that most user agents can't decode "Outlook
Rich Text" but the sending Outlook is configured to use HTML, not Rich
Text. I changed the global setting to Plain Text and all was well, but
setting it back to HTML brought back the problem.

I've worked around this for now by setting up a contact for the OE user
which forces Outlook to send as Plain Text, and attachments sent
subsequently can be detected and opened. However, I'd like a fix for
this, as the sending user prefers to be able to send colourful emails
and at the moment any other OE user won't be able to decode any
attachments she sends.

Any ideas?

This is one of those problems whose search terms are so similar to an
unrelated but common problem (alluded to above) that Google is no help
at all!

Phil, London

 

[Gordon]

Attachments sent by just one of our users from Outlook 2003 (fully
updated) cannot be read by another user in Outlook Express.

The default Outlook Mail format is Rich Text. Only Outlook (not Outlook
EXPRESS) can read this type of mail format.
Change the Mail format of this User to either Plain Text or HTML, then you
should find that the OE user will be able to see the attachments....

 

[Philip Herlihy]

The default Outlook Mail format is Rich Text. Only Outlook (not Outlook
EXPRESS) can read this type of mail format.
Change the Mail format of this User to either Plain Text or HTML, then
you should find that the OE user will be able to see the attachments....

Thanks for the reply, but (as I said) I'd tried that. It seems to be
"stuck" in Rich Text regardless.

I understood it's well-known that most user agents can't decode
"Outlook Rich Text" but the sending Outlook is configured to use HTML,
not Rich Text. I changed the global setting to Plain Text and all was
well, but setting it back to HTML brought back the problem.

Phil

 

[Peter Foldes]

It sure look like (from the message source ) that is Windows Mail on a 64bit and not
Outlook Express. Can you verify please

 

[Philip Herlihy]

It sure look like (from the message source ) that is Windows Mail on a
64bit and not Outlook Express. Can you verify please

Definitely Outlook Express on a 32-bit machine.

Phil

 

[Diane Poremsky [MVP]]

Check the affected person's contact - is it set for rich text only?

We do see a problem now and again where html seems to have the problem and
plain text fixes it, but I don't recall a cause - the solution is just to
use plain text to resend.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[Diane Poremsky [MVP]]

This determination was made from the content-type snippet he posted?

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.