Winmail.dat received only by some users
I have searched high and low and done everything suggessted when it comes to winmail.dat attachments. However, I cannot find a solution to something that just started happening 10 days ago.
Running Exchange 2010 all SP and rollups. Users have outlook 2010.
As stated 10 days ago, a couple users started getting emails with winmail.dat attachments from outside emails. These other companies are using exchange 2003, 2007 and 2010 (various companies). When I am copied on the emails (testing solutions
for this problem) all attachments come through normally, but the 2 users that I am working with are still getting winmail.dat attachments.
Figured I'd eliminate outlook and just check OWA. The 2 users OWA accounts (outlook is closed and not running at all at this point) still have the winmail.dat attachments in OWA. This is the part that is most confusing to me as it seems like
a issue with their mailboxes as it is now happening without outlook involved.
In addition to the RTF settings on the exchange server, HTML/plain test settings on the clients, we have also removed any rules and deleted the contacts in the users contact folder just to be sure there isn't anything funky there. Also checked
with the senders, they are all using outlook 2007 or 2010 and sending emails as HTML and as mentioned earlier, all these companies are using exchange 2003 or later.
What am I missing?
March 30th, 2011 4:15pm
Quote: “The 2 users OWA accounts (outlook is closed and not running at
all at this point) still have the winmail.dat attachments in OWA”
Does the issue happen permanently for these two users, and only to these two users?
Please check the message headers on the problematic messages
Please enable the pipeline tracing and content conversion tracing, send the test message from senders to the problematic recipients again, and then check
the copies of the message
Resources:
Enable Pipeline Tracing
Content Conversion Tracing
How e-mail message formats affect Internet e-mail messages in Outlook
James Luo
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 1:54am
Yes, it's consistent for these 2 users.
I have enabled tracing so we'll see what we get. I don't see anything strange in the header info on any of the emails. I can post some of them here but is there anything I should be looking at specifically?
March 31st, 2011 9:51am
That's strange, that typically happens to contacts but not MEUs. If you get stumped, I'd be inclined to move the mailbox to another store as this will create a new mailbox. (incase there is mailbox corruption)James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 8:09pm
After send mail to both of the problematic user and the working user, you can then compare two copies, and seek for the difference.
Agree with Chong. If the message is identical, the issue would be related to the problematic mailbox itself, moving mailbox could fix certain corruptionPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 31st, 2011 11:23pm
James and James,
Headers look identical. Tracing is not really turning up anything compared to tracing on "normal" messages that aren't getting the winmail.dat. Your suggesstion to move to another store was in the back of my head, but I was waiting to see if
someone else felt that course of action was the next step. I'll do that and report back. Thanks
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 7:59am
Did moving the mailbox solve the problem?
May 11th, 2011 10:58am