If messages are sent using the Exchange family of mail programs
(includes Windows Messaging or Outlook97/98/2000+) and the option to use
Rich Text Format is selected, it puts the RTF message (and any attached
files) in an attachment called WINMAIL.DAT (application/ms-tnef). But
this attachment is useless to most other mail programs. In some mail
programs (e.g. Outlook Express, Windows Mail, Windows Live Mail), the
attachment won't even be visible.

The Exchange user can turn off the RTF option for messages to selected
recipients. Note that if sending via an Exchange server, the Exchange
server administrator may be overriding the mail client settings. In
this case, the administrator will need to make changes on the server.
In some cases, the Exchange server actually removes the attachments to
some recipients.

For additional information, see the MS-TNEF WINMAIL.DAT Attachments
section of
Decoding Internet Attachments - A Tutorial
http://TechHelp.Santovec.us/decode.htm#ms-tnef

--

Mike - http://TechHelp.Santovec.us



"mikelee101" mikelee101athotmaildotcom wrote in message
...
Hello,
I'm seeing an issue that confuses me, and was hoping someone could
give me a
suggestion or two.
We use POP3 email at our office. Some users run Outlook while others
use
Outlook Express. I am running Outlook 07. One of the Outlook Express
users
never receives attachments from me. The message comes through just
fine, but
no attachment. There is no .dat file or .txt file or any notice that
an
attachment has been stripped, it's as if the attachment never existed.
Other
OE users in the office receive attachments from me just fine. Not
being that
familiar with OE, I was hoping someone might know if there's a
security
setting somewhere about downloading attachments. I did see the option
about
not opening attachments that could potentially be a virus, but the
users who
do receive attachments from me have that checked, so it wouldn't seem
that
could be it. (I didn't see anything in the security settings on our
mail
platform that looked like it could be the culprit.)
All of our OE users are running OE6, XPPro. Any suggestions would be
greatly appreciated.

--
Mike Lee
McKinney,TX USA