Mark
asked on
cannot open winmail.dat attachments
I have a Vista workstation in a SBS 2008 domain. When this user sends emails with attachments using Outlook, they are send as a winmail.dat file. That is fine if the recipient is using Outlook, but these attachments cannot be opened on computers which do not use Outlook or an Outlook compatible reader. This only started happening recently with our conversion from SBS 2003 t0 SBS 2008, so I think something in this user's profile may have been changed. Before, this user on this same Vista workstation could send normal, mime encoded attachments that could be opened by non-Outlook mail readers.
Is there some setting in this user's Outlook, or in Exchange that I can set to fix this problem? I've looked around and nothing jumps out at me.
Is there some setting in this user's Outlook, or in Exchange that I can set to fix this problem? I've looked around and nothing jumps out at me.
In what format the emails are sent HTML? RTF? Plain text?
chances are he is sending as RTF.
Change that to HTML and this particular problem will go away.
Many (especially non Exchange) mail servers will not understand the TNEF/ STNEF coding of RTF and Exchange and will simply encapsulate the attachments as a winmail.dat file.
Change that to HTML and this particular problem will go away.
Many (especially non Exchange) mail servers will not understand the TNEF/ STNEF coding of RTF and Exchange and will simply encapsulate the attachments as a winmail.dat file.
ASKER
The user often does a print-screen of something, then opens a Word doc and pastes the image. Then the user sends the doc as an attachment. I don't know if she is using the sent to function in Word, or attaching the doc in Outlook.
Does that matter?
Where would I have her change settings from rtf to html? I don't have a vista version of Outlook handy. I'll have to log into her computer after hours to make any change.
Does that matter?
Where would I have her change settings from rtf to html? I don't have a vista version of Outlook handy. I'll have to log into her computer after hours to make any change.
Go to Tools menu, click Options, and then click the Mail Format tab.
In the Compose in this message format list, click the HTML and check if it helped.
In the Compose in this message format list, click the HTML and check if it helped.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry for the delay ...
Commandosk: HTML format was already set.
maxsmith5k: It appears that the comments in your link (33491457) did the trick. I've put only the Linux domain into the Organization Configuration > Hub Transport, and attachments seem to be back to normal mime attachments, not winmail.dat. THX.
Commandosk: HTML format was already set.
maxsmith5k: It appears that the comments in your link (33491457) did the trick. I've put only the Linux domain into the Organization Configuration > Hub Transport, and attachments seem to be back to normal mime attachments, not winmail.dat. THX.