PC Review


Reply
Thread Tools Rate Thread

Attachment encoding problem

 
 
Philip Herlihy
Guest
Posts: n/a
 
      8th Jun 2009
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
 
Reply With Quote
 
 
 
 
Philip Herlihy
Guest
Posts: n/a
 
      10th Jun 2009
Philip Herlihy wrote:
> 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


Noone has any ideas?

Phil
 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
.NET 2.0 - Sending Emails - Subject and Attachment Name Encoding Issues Shan Plourde Microsoft Dot NET Framework 14 24th Aug 2007 02:29 PM
how does ado.net SqlDataReader.GetString() know which encoding to read the data into a string as? Does sql sever set this at the column data type level, server wide encoding setting, os encoding? Daniel Microsoft Dot NET Framework 1 8th Mar 2007 11:06 AM
how does ado.net SqlDataReader.GetString() know which encoding to read the data into a string as? Does sql sever set this at the column data type level, server wide encoding setting, os encoding? Daniel Microsoft ADO .NET 0 7th Mar 2007 11:15 PM
how does ado.net SqlDataReader.GetString() know which encoding to read the data into a string as? Does sql sever set this at the column data type level, server wide encoding setting, os encoding? Daniel Microsoft Dot NET 0 7th Mar 2007 11:12 PM
Different encoding? ( problem on Chinese encoding on textbox ... ) Boki Microsoft VB .NET 1 28th Apr 2006 10:07 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:44 PM.