Angel,
We deal with this issue all the time... here's a copy of the message I always send out
to our users:
=========================
Here's a definitive resolution for the whole "winmail.dat" issue.
If you, as an Outlook 97/98/2000 user, send e-mail formatted as Rich Text (RTF), and
you send it to a person whose mail client does not support RTF, then that person will
receive a plain text message, and everything else - attachments included - will be
wrapped up into an unreadable "winmail.dat" file.
There are two ways for Outlook users to prevent this from happening:
1.) When composing new messages, make sure to set the format to "Plain Text" (Format
menu -> Plain Text).
2.) When sending to a recipient that you know has no RTF mail capabilities, modify
the recipient's contact record to indicate this. Go to your address book, click once
on a contact name, then click the "Properties" button. Then, click on the folder tab
that says "Name," and at the bottom of the window you'll see a checkbox that says,
"Send e-mail using plain text only." Check this box, save the changes, and you're all
set.
More info and links can be found in the MS Support Knowledgebase, at the following URL:
http://support.microsoft.com/support/kb/articles/Q196/7/84.ASP?LN=EN-US&SD=gn&FR=0
Please circulate this info to anyone who's been sending you "winmail.dat" files lately.
=========================
Hope that helps,
Jordan
---------- Original Message ----------------------------------
From: "Angel Castillo" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 6 Jun 2000 12:21:20 -0500
>Ok, I have a user who's claiming that when they try to send an attachment
>the user receiving the attachment receives the attachment that I've included
>in this e-mail. It's called "winmail.dat" Does anyone know what this is
>all about?
>
>Here is the message that our user gave us explaining the situation:
>
>"I sent the letter below to a client. His response was that, while he could
>read the letter, he could not open the attachment. I did not include an
>attachment. Is this "mystery attachment" perhaps caused by the font that I
>use for my email address? I have gotten this same response from other
>clients--but not all of them. But, I don't always use the same font on my
>signature. This is the only thing I can think of. Or, does it have
>anything to do with the fact that I send stuff in Message Rich Text? Or
>perhaps it has to do with the system that is receiving the document.
>
>Please help me figure this out because I would like to eliminate the
>confusion of the "mystery attachment". By the way, here is the attachment
>that shows up on return emails from said clients."
>
>Now, I think the Rich Text part has something to do with it, but I'm not
>sure if the type of font being used is a problem. I also noticed that the
>attachment comes embedded within the e-mail body which I believe I've seen
>on this list in regards to Rich Text being the culprit. Any ideas will be
>greatly appreciated.
>
>Thanks
>
>-------------------------------------
>Angel Castillo, MCSE, MCP+I
>MIS Dept. Jobs.com
>IMail System Administrator
>[EMAIL PROTECTED]
>(214) 273-7629
>"When you love what you do...you're alive!"
>
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
