B
bill
I have a user running outlook 2000, exchange 2000. they send a message to an
internet based recipient and the recipient gets the winmail.dat attachment
instead of the actual attached file. had the user send via plain text, this
seemed to work but their testing may have been flawed (they sent with no
attachment for the test). user later tells me that the problem returned. I
investigated closer and found that a message that she sent out to her own
yahoo account was sent as plain text ( per the message in her sent items) but
when we look at the headers in yahoo, they show "content type:
multipart/mixed" so basically messages sent as plain text are arriving as RTF
or ???. of course this problem started out of the blue about a week ago with
no apparent changes to her client or the server.
internet based recipient and the recipient gets the winmail.dat attachment
instead of the actual attached file. had the user send via plain text, this
seemed to work but their testing may have been flawed (they sent with no
attachment for the test). user later tells me that the problem returned. I
investigated closer and found that a message that she sent out to her own
yahoo account was sent as plain text ( per the message in her sent items) but
when we look at the headers in yahoo, they show "content type:
multipart/mixed" so basically messages sent as plain text are arriving as RTF
or ???. of course this problem started out of the blue about a week ago with
no apparent changes to her client or the server.