Winmail.Dat from Outlook 2003 to an Outlook client(XP or 2003)

[Guest]

I am sending a 6mb zip file to myself and when I get it the zip is
automatically changed to a winmail.dat file. I have changed sending to plain
text and done all the things on the microsoft sight but still I get this
annoying winmail.dat. It is happening to a few other people here too. Just
certain attachments are changing. I am not sending this outside the company
to different email environments just sending it to myself or another Outlook
user. Is it server side. I found one thing server side dealing with RTF but
that didn't fix it either. We are running Exchange 2000 (all Service Packs).
Any ideas!!!!!!!!!!

 

[Brian Tillman]

I am sending a 6mb zip file to myself and when I get it the zip is
automatically changed to a winmail.dat file. I have changed sending
to plain text and done all the things on the microsoft sight but
still I get this annoying winmail.dat.

However, if the Contact entry for the address to which you are sending it
has "send in Rich Text only" selected, it doesn't matter what format you
chose.

 

[Guest]

I am using the a name from the global address list not an outside contact. I
send it to myself (jsmith to jsmith). It leaves correctly using plain text
format and when I get it back it is winmail.dat. Is there a way to change
what a global address users send in Rich text only property you spoke about.
It doesn't happen to every attachment but it happens with this 6mb cisco vpn
zip file and a few others that I've seen. I've sent it to my yahoo account
and set it to plain text and it sent fine. It happens only from global
address user to global address user using outlook 2003 to xp or 2003 using
exchange 2000.

 

[Brian Tillman]

I am using the a name from the global address list not an outside
contact. I send it to myself (jsmith to jsmith). It leaves correctly
using plain text format and when I get it back it is winmail.dat.

Sounds to me like an Exchange artifact (perhaps because it KNOWS both sender
and recipient are under its pervue and that the recipient can therefore
handle the TNEF attachment). I know next to nothing about Exchange and you
may get a better response in an Exchange newsgroup.