I sometimes receive winmail.dat as attachment

I sometimes receive winmail.dat as mail attachements though senders' Outlook or Exchange are properly configured (html). A colleage of mine sitting next to me with OS Lion, connected to the same ISP, gets the same mails from the same sender with the right attachments.
Might it happen that the issue lies with the mail server of the ISP?
Thanks for your help
Patrice

Thank you very much
I knew TNEF's Enough and it has worked well so far . TNEF's is symptom fighting. I am looking for the cause.
Rgds
Phalch

Similar Messages

Why I receive Winmail.Dat instead of list of attachments with Email?

I am receiving Winmail.DAT file as an attachment with email that contain large attachments. I can not view the Attachments, nor can I reterive this .dat file. How can I change the settings in MAIL. Any body can guide plz.?

Mac OS X Mail: What is a winmail.dat attachment? : Apple ...
Download TNEFs Enough for Mac - Extract winmail.dat ...
Winmail.dat | OfficeforMacHelp.com
How to Open Winmail.dat Files | Mac|Life

One user receiving WINMAIL.DAT attachments from one or two domains

I have a single user in our organization that is RECEIVING WINMAIL.DAT attachments which contain PDF's from only one or two domains external to the organization.
Let me be clear that he is not sending out WINMAIL.DAT attachments to anyone. I have tested sending him RTF emails with a PDF attachment from an external address and he is receiving them just fine. We are running two Exchange 2013 servers in
HA configuration and this user is using Outlook 2010 for his email client. If he looks at these messages in OWA, they still have the WINMAIL.DAT attachment within OWA. I cannot find an answer for this anywhere, and this is not related to disabling TNEF on
our exchange servers. Does anyone have any ideas? I would really appreciate the assistance.
Thanks,
Dean

Hi
Did you try this article -
http://support.microsoft.com/kb/278061/en-us
If the above article did not help then you can try the following
1) Create an external contact for sender email address from whom the email is sent to the affected user.
Run the below command for that sender external contact
Set-MailContact "External Contact" -UseMapiRichTexFormat Never
Ask the user to send email once again to that affected recipient and see if it still occurs.
Most likely the latter should fix your problem.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Changing outlook 2013 contact so they will not receive winmail.dat files - missing settings

trying to change email properties of a contact in outlook 2013 who keeps receiving winmail.dat from one of our guys , trying to get to internet format to change that setting.
I have made the registry change suggested here http://www.slipstick.com/outlook/use-outlooks-contacts-contact-cards/
but though I can get to properties now, I still do not see Internet Format.
I do not even see it when I create a new contact.
what am I missing?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Best Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook 2007 Clients receiving winmail.dat attachments

I am running Exchange 2007 on Windows 2003 R2 64 bit. End users run Outlook 2007 on XP sp2 machines. Users randomly receive winmail.dat attachments in their email. Does anyone know how to fix this on Exchange 2007?

That is what I find most interesting, is what Microsoft has released regarding winmail.dat files. It seemed to me that it was the mail compliance of the recipient that was causing these files to appear. Only recently have I found more discussion on the topic on other forums, including here, showing that it is also caused by other situational basis other than the recipients method of viewing the email...unless I misunderstood all along and it would seem so. Because in my mind, it would make more sense if the recipients mail server is the cause of the issue, not so much the recipient. if the recipients mail server does not interpret TNEF than could all their customers be experiencing this? i must assume this because it would mean that if the recipient accesses their email via a webmail client that does not support TNEF, than they receive a winmail.dat...however if they check their email again from outlook or someform of email program that does understand TNEF, than shouldn't the email and attachments show up properly? It is my experience that they do not. That is how I began thinking that it must be the mail server of the recipient that is causing this.
I tried setting the 1 user's outlook to send only plain text...I am waiting to hear the results, but they were already set to send in HTML only. By my understanding is that TNEF is created only when RTF is used for outbound email, and HTML and Plain Text do not create TNEF...punch me if I'm wrong

Receiving winmail.dat attachments instead of what was originally sent

Having trouble receiving an attachment . usually sent as PDF. See them on verizon.net as winamail.dat. And will not download to Windows live mail as an attachment at all. Was working in December. Not sure what happened.

My I suggest my product Letter Opener Mobile for iPhones and iPads. Or for Macs Letter Opener Pro, which converts winmail.dat files right inside Mail application, and Letter Opener Lite.
I may receive some form of compensation, financial or otherwise, from my recommendation or link.
<Edited by Host>

Winmail.dat attachment

I sometimes forward a file from my office (PC) to my home email address. The attachment I recently tried to send was a word document, but was received as a winmail.dat file. I have made the changes in Outlook to supposedly resolve this issue, i.e. changed the settings to HTML, but still receiving winmail.dat. I also have Office 2004 installed on the imac. I noted that there is third party shareware available to "resolve" this issue. Is there another solution?

The Apple Mail Plug-in OMiC process Microsoft Outlook winmail.dat files.

How to open winmail.dat attachment on N95

Hi everyone
please help
V10.0.018
15-03-07
RM-159
Nokia N95(09.01)
I have a nokia N95 and when i recieve any email attachment which is excel file or word file by email it is shown as winmail.dat and i cannot open the file or even save it with a differnet name or extension however if i send the file with bluetooth from my computer to the phone it is opened and read perfect
1- we use exchange server 2003
2- outlook 2003 as a client
I know that exchange sends these files in rtf format is there a work around so i can read my documents !!!Message Edited by amrlotus on 12-Apr-200702:48 PM

I tried changing the extension, which sort of works. I sent an email to my wife's iMac from my PC, which had several .jpg and one .pdf files attached. It shows up in Mail with a single winmail.dat file attached. I changed it to a.pdf, and it opened the pdfonly. I couldn't get the jpgs to open, even with a .jpg extesion.
First of all, why in the world would it do this? Second, how do I open them since they are mixed type, and several at once? Seems ridiculaous that a Mac does this to attachments, BTW.
Message was edited by: wrench75

TNEF Issue - Winmail.dat or messages stuck in submission queue

Hi guys,
I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails.
Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
Current Environment Configuration:
I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
Hi,
According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
I recommend that you refer to the following article to solve the issue:
http://support.microsoft.com/kb/278061
Method 1: Change the default message format
The sender can change the format of the email messages that they send by using the following steps:
On the Tools menu, click Options, and then click
Mail Format.
In Compose in this message format, click to select Plain Text, and then click
OK.
NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
Method 2: Modify the recipient's entry in the Personal Address Book
The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:
On the Tools menu, click Address Book.
In Show Names From, click the Personal Address Book.
Select the addressee that you want to set as plain text, and then click
Properties on the File menu.
In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
OK.
Method 3: Change the specific contact format
The sender can use the following steps to set plain text in the recipient's contact record:
Open the recipient's record in the Contacts folder.
Double-click the recipient's e-mail address.
In the E-Mail Properties dialog box, click Send Plain Text only under
Internet Format.
Method 4: Set the Outlook Rich Text Format Internet e-mail setting
In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
Click the Mail Format tab.
Click Internet Format.
Under Outlook Rich Text options, click either Convert to HTML format or
Convert to Plain Text format.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Niko,
The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure".

How can I get Mac mail to open winmail.dat attachments on lion 10.7.3

How can I get Mac mail to open letter attachments winmail.dat?? (Lion 10.7.3) Any help appreciated...

Sorry peterskine,
it's true in part. There's more then one article on the subject "Recipients receive a winmail.dat attachment":
http://office.microsoft.com/en-gb/outlook-help/recipients-receive-a-winmail-dat- attachment-HA010153018.aspx?CTT=1
The odd thing is that my colleague and me use the same release mountain lion and we received the same email from someone on Outlook2007. He received the mail with the attachment, whilst I saw a "Winmail.dat". It already happened to me on snow-leopard, some month ago. Up til today I don't know what the difference between our machines is.
But it is interesting: the same OS, the same mail-clients (Apple Mail) and still different results.
Note: on my machine it used to work properly. It just suddenly happened that I started to receive winmail.dat files in stead of proper attachments.
When I have more time on hand, I cant try to find out why this happens.

Exchange 2010 sends attachments as winmail.dat

Hi
Some users are complaining about pdf attachements they received as winmail.dat. This is an internally isue.
For external mail flow I disabled tnef conversion, seems to work. Is there a possibility to do the same thing for the internal mail flow?
Regards
Peter

Hi PeterN22,
Winmail.dat attachments are included in received e-mail messages is because the Winmail.dat file is used to preserve formatting that the sending
client includes in the message, but the receiving client does not recognize the Winmail.dat file.(The original message attachment is not always separate from the Winmail.dat file attachment, and may be included in the Winmail.dat file attachment.)
So it is important to clarify what clients were involved in both the sending and receiving the messages in question.
If this is occur in Outlook, here is a related document for you:
Winmail.dat attachments are included in received e-mail messages in Outlook
http://support.microsoft.com/kb/278061
Thanks,
Evan
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.

Winmail.dat attachments from Exchange 2013 on premi and Hosted Office 365 set up.

Hello TechNet,
I have an on going situation with winmail.dat attachments. I currently have a ticket open with Microsoft, but I want to see if anyone has personal experience with this. Here is the rundown.
We have migrated from an Exchange 2007 server to Exchange 2013 for the migration to Office 365. We also have a hosted Office 365 server with half of our mailboxes in the cloud and half of them on the Exchange 2013 on premise server.
The current settings for TNEFEnabled:
On Premise: False
Hosted: False
Whenever a internal email with a calendar invite(exchange calendar, go to meeting) goes out to any external domain the recipients receive winmail.dat.
When settings for TNEFEnabled On Premise and Hosted are set to true both calendar invites and PDF, Excel attachments etc the recipients receive winmail.dat.
When speaking with Microsoft about this issue. The representative was watching me through a LogMeIn session as I set both TNEFEnabled false on both on Premise and Hosted.
This is really frustrating as many employees depend on this to be fully functional, and to be honest am tired of dealing with this.
I need help.
-Ben

I am having the same issue.
Luckily I have only migrated my own mailbox to office365.
Tried both true and false TNEFEnabled on both onpremise and office365 via powershell and confirmed that both have been applied.
If I send the email as a plain text then the attachment works ok. If I send it as HTML then I get winmail.dat.
The above KB doesnt really help me, sending plain text emails is like going back to the dark ages!
I am sending from outlook to outlook (I send from my external email address, to my work email address and visa-versa)
If someone with an onpremise mailbox sends me an email, the attachment works ok.
If someone sends me an attachment via hotmail, the attachment works ok.
It seems to only effect emails I send to myself through outlook, i am sending it through a POP3 account to our onpremise exchange 2010 which forwards the email to office365

New mails received after IOS 5.0.1 update do not show graphics but instead unviewable file name and an attachment winmail.dat

I sent out a mail, composed by outlook 2007 in HTML format this afternoon which contained graphics, to several of my friends and copied myself. All of them had duly received the mail and were able to see the graphics in the mail in their iphones or ipads. However, the copy that was extended to myself had only the unviewable graphic filename and also an attachment winmail.dat(which cannot be opened) from both my iphone and ipad (both updated with IOS 5.0.1). Prior to this update, I had no problem of seeing graphics or photos in the mails received in both my ipad or iphone. I ran couple of test mails and they all ended up the same.
Any ideas??

Turned out, it's the Microsoft SP3 update that caused the problem.

I recently purchased an Iphone 6plus and I am receiving pdf attachments that are shown as winmail.dat attachments on the phone. When I check e-mail via my macbook pro the attachment is a pdf and I can open it. Why is this happening?

I recently purchased an Iphone 6plus and I am receiving pdf attachments that are shown as winmail.dat attachments on the iphone. When I check the same e-mail on my macbook pro the attachment is a pdf and I can open it. Why is this happening?

I had this problem too after i upgdatd to OS X Mavericks... only the songs on my iphone 5s that i purchased from itunes would play.
i read something about it being a syncing issue. when you plug your phone into your computer with the usb cable, the person said to switch from automatic syncing of itunes to the "manual" option. mine was already set to manual so i wasn't sure anything would work. BUT, when i plugged my phone into my computer, it started to sync all of my music on my phone again (top of itunes bar where song playing/time is listed said "now syncing 123/534 songs to x's iphone"). once that was completed, i checked the music app on my iphone and everything was back to normal!
so, i would suggest setting your music syncing settings to manual if you haven't tried that yet!
hope this helps!

Attachements showing up as winmail.dat

I just moved from a Windows XP machine to a MAC and I'm having problems receiving attachements.
I'm using Entourage as my mail client.
I've sent some emails containing attachments to myself recently from my Windows machine using Outlook 2003 and to other people with our company.
When look at the email on my MAC their is no attachment but a winmail.dat file.
If I look at the email back on my windows machine it is corrrect (Both Outlook and Entourage are configured to check the same account). I quized the other people within our company as they are also using MACs and they stated the attachments came thru fine.
Any idea why the problem seems to be unique to my new MAC?
Regards,
Mike
Mac OS X (10.4.6)
Mac OS X (10.4.6)

The above answers are absolutely correct. And to give a little more information on this problem, I am quoting this almost verbatim from John Rizzo's recent article in MacWorld magazine:
=================
It's bound to happen. Occasionally, you'll receive an un-openable email attachment named winmail.dat from one of your Windows friends, and he or she will insist that the attachment was a Microsoft Word file or some other type of a file.
First things first: DON'T BLAME YOUR MAC!! The fault lies on the Windows side, in Exchange Server & Outlook for Windows. When Outlook sends an email message in Rich Text Format over the Internet, Exchange Server sometimes creates an attachment called Winmail.dat, containing the message and some encoding data.
One quick fix is to download and install the utility "TNEF's Enough" on your Mac:
http://www.joshjacob.com/macdev/tnef/index.html
This utility can extract a Mac-usable file from a Winmail.dat attachment in a few seconds.
But running that utility all the time will get old pretty quickly if your friends are sending you lots of attachments and they're all winmail.dat files. If you're getting lots of attachments like this, an even better fix is to ask your Windows friends to turn off RTF in Outlook for Windows. They would choose Tools->Options, select the "Mail Format" tab, and then specify "Plain Text" in the "Send In This Message Format" list, and then click on OK. Once they do that, you will not receive those winmail.dat files in the future.
OR, the best of all fix would be for them to point their network administrators to the Microsoft Knowledge Base article "How to Prevent the winmail.dat file from being sent to Internet Users" at http://support.microsoft.com/kb/q138053/
Power Mac G4 QuickSilver Dual 800 MHz Mac OS X (10.4.4)

I sometimes receive winmail.dat as attachment

Similar Messages

Maybe you are looking for