Winmail.dat Issues

I have a friend who sends me Outlook email with imbedded images. I receive text with an attachment called "winmail.dat".
I've never been able to see these images in any version of Mail, including 4.3.
But now, my wife, who has an iMac which also runs OS 10.6.4 and uses Apple Mail 4.3 is receiving the same emails, and the images display fine!
I've been complaining to my friend that he needs to change his Outlook settings. But it now appears that the issue is on my Mac Pro. Any ideas?

I am having EXACT same issue. Right down to the wife being able to open the files. In fact, they don't come in to her Mail as winmail.dat, they appear as normal files (PDF or DOC, etc.). Yet, I can't see them unless I use Safari to go to Gmail's site. This is really annoying as it's our boss sending these. It also happens on my iPhone. Any ideas???

Similar Messages

PDF Submit button creates winmail.dat issue...

Hi all,
I am attempting to create a fillable form (PDF) which includes a submit button, which on clicking attaches itself to an e-mail (Outlook 2013), populates the recipients, subject and body text. I have created the document (using a submit form button) and it works perfectly apart from one very large problem... when sent within our company the e-mail is quarantined!
Having spoken to messaging team it appears that this is due to a winmail.dat file.
I am hoping someone can provide some assistance, is the winmail.bat file created by InDesign, or by Acrobat, and is there a way to bypass this/other method to avoid the problem?
Any suggestions welcome.
Thanks

I don't think this file is created by Indesign, Acrobat or any other Adobe software.
I found this http://support.microsoft.com/kb/278061 on searching.
As it state "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 would suggest you follow the suggestion in the link above and then check, if it helps.
You can also look at these links :- http://support.microsoft.com/kb/138053 and http://support.microsoft.com/kb/149203
--Manish

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".

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!

HT1338 pdf attachments and excel spreadsheet attachments are opening as winmail.dat and the pages are blank when you open them.

All of a sudden the e-mail attachments I send to my MacBook Pro from my PC Laptop open up as winmail.dat as a blank sheet of paper. This only started happening within the last week. Before that everything was fine. I check my PC and confirmed the attachments are set up to be sent in HTML. Any suggestions?

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

Winmail.dat attachments after importing PST into online archive

Hi, we enabled the online archive feature on one of our Office365 exchange account. Later, we used the PST capture tool to import a PST file into the archive. Now after importing, the user came back saying he sees winmail.dat files as attachments. Prior
to uploading the PST to the online archive the attachments were visible normally. The PST file belongs to the same user. Its an old PST file attached to his mailbox since a long time. We then subscribed to the online archive plan for his account and used the
PST capture tool for importing the emails. To isolate the cause of the issue we tried dragging an email with an attachment from themailbox to the online archive from within Outlook. The moved email appeared correctly with attachment in his archive. We have
not tried importing the whole PST from within outlook, as the size of the PST is too large (32 GB). Could someone please help resolve the issue.
Thanks in advance.

I recommend that you post this in the Office 365 Exchange Online Forum:
http://community.office365.com/en-us/forums/158.aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Winmail.dat

Why are my attachements only recently coming in as winmail.dat? I have never had issues opening word, pdf or excel docs on iphone or ipad in the past. I have the doc 2 go app as well so I don't know why suddenly they don't open??

Bvjed et al.
My wife has just had this issue and after digging around I found what was causing HER issue.
Situation:
Some email recipients were receiving a .pdf file as a winmail.dat file but this was not everyone and only affected those on iPad/iPhone that could not receive/interpret RTF formatted emails. Anyone opening the email on a Windows PC (and I haven't tested on Mac or other devices such as Android etc) would see the .pdf attachment and it would open normally.
Analysis:
There are plenty of advise/recommendations saying that .pdf files attached to emails formatted in RTF format may not be able to be received if the receiving client cannot handle RTF. HOWEVER, it is important to understand HOW emails are converted/formatted in RTF by Outlook (various versions). One method that most users have checked is the Mail Format setting within each email as either HTML, Rich Text or Plain Text. The other method that is much less obvious is the setting at each email address level and you can check this by right-clicking on the recipient's email address and selecting Outlook Properties. Assuming you do not have the person's contact details in a contact record, it will show a small Email Properties window. Note the last field called Internet Format and if it states "Send using Outlook Rich Text Format" then that recipient would be unable to open .pdf attachments that you send them if they are using an IOS mobile device.
Solution:
Change this value to "Let Outlook decide the best sending format" and send the email & attachment again.
This explains why some people found the solution to be deleting the entry from their Outlook Contacts - it someone reinstated the format option to the "Send using Outlook Rich Text Format" for future emails. How that happens is for someone else to determine! ;-)
Please like this if it helps you.
Cheers
Mark

TS3276 why is jpeg file lost and replaced with winmail.dat file in mail

I sent a jpeg file to my hotmail account, which is synchronised in my Mac Mail but the file was lost/converted to winmail.dat attachment, which I couldn't import to iPhoto. How do I import a jpeg image, emailed to me from an external source, to iPhoto?

I think you need to configure Outlook in Windows to use HTML messages.
Here is Microsoft's incomprehensible support document on the issue.
Here is one from about.com that makes sense.

How do I open Winmail.dat?

How do I open Winmail.dat?

ajlayne wrote:
In Outlook, I changed the setting for how the mail sent to each typoe to resolve the issue. I created one email per setting and addressed to both people on their corporate exchange account (same server for both) and their gmail accounts. This is where the confusion arose since one phone receives fine and the other doesn't. I used Gmail as an alternate mail client with the same result.
So basically I used two different clients each time sending to four addresses two are located on each phone. Phone A always receives a winmail.dat file no matter which client or email address is used. Phone B always receives the attachment in it's correct format.
I took it a step further and used the phones to test sending. Even if I use Phone A to send to the other account on Phone A, winmail.dat is received. If done from Phone B to Phone A, Phone A winmail.dat persists. Phone A to Phone B correct format is received. I'm thinking there is a setting somewhere on Phone A I'm not aware of that was somehow changed since it is not mail client dependant nor recipient mail server dependant based on the testing results.
This is a Microsoft Windows setting with Microsoft Outlook or within the Exchange Server gateway in general. These winmail.dat files have been arriving on Linux, BSD, OS X, Tru64 Unix, ULTRIX, Solaris and many other servers for many years, too — unfortunately, everybody that's using non-Microsoft clients and tools encounters these files from time to time. The winmail.dat is a Windows Mail data file, after all.
If the mail client or if the mail server gateway sends a mail message to an iOS device — or many other "foreign" mail clients — that involves a winmail.dat file generated by the sending client or generated by the originating mail server gateway, then iOS will show the winmail.dat file. Like many other mail clients, the iOS mail client does not decode, process nor create these winmail.dat files. (Most clients simply treat these winmail.dat files as an arbitrary attachment on the message.)
Send the same messages to the same email addresses and read those messages via another mail client — one that doesn't have winmail.dat support — and you'll see the exact same behavior; a wad of attached winmail.dat data.
From Microsoft: How to Prevent the Winmail.dat File from Being Sent to Internet Users. In short, either the Outlook client settings or the Exchange Server (IMC) settings will need to be changed here.

Winmail.dat Attachments are received whether TNEF is disabled or not

Hi,
we've got some issues when sending emails to some linux recipients, that attachments or s/mime signed emails are converted to the dreaded winmail.dat attachements.
On Exchange 2010 i've just configured the corresponding remote domain (or the default one) to disable TNEF sending to this mail domain.
Apparently with Exchange 2013 this setting does not work anymore. With setting the parameter "TNEFenabled" to $false, the recipients still get winmail.dat attachments.
do you have any idea how to work this out?
Kind regards,
Peter

Hi,
attached you will find the headers of an email which got that issue.
Return-Path: <[email protected]>
X-Original-To: [email protected]
Delivered-To: [email protected]
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network
Received: from DOX13FE02.hex2013.com (DOX13FE02.hex2013.com [128.127.69.77])
by web31.dogado.de (Postfix) with ESMTPS id 507B122E53F2
for <[email protected]>; Fri, 10 Jan 2014 10:45:39 +0100 (CET)
Received: from DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) by
DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) with Microsoft
SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:41 +0100
Received: from DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by
DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) with Microsoft
SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:40 +0100
Received: from DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff]) by
DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff%14]) with mapi id
15.00.0775.031; Fri, 10 Jan 2014 10:45:40 +0100
From: Peter Stutzinger <[email protected]>
To: "[email protected]" <[email protected]>
Subject: TNEF Testmail
Thread-Topic: TNEF Testmail
Thread-Index: Ac8N6LQ/yN5XQruBSFWwYuW7AIuW3g==
Date: Fri, 10 Jan 2014 10:45:39 +0100
Message-ID: <[email protected]>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
X-Originating-IP: [128.127.69.74]
Content-Type: multipart/mixed;
boundary="_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_"
X-HEX2013-Disclaimer: true
--_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Herzliche Gruesse aus Duesseldorf
Peter Stutzinger, Enterprise Architect - Messaging
dogado Internet GmbH
Saarlandstr. 25
44139 Dortmund / DE
Tel.: +49 (231) 28 66 20 0
Fax: +49 (231) 28 66 20 20
Profil auf XING: http://www.xing.com/profile/Peter_Stutzinger
Corporate-Blog: http://www.webhostingblog.de
Twitter: https://twitter.com/dogado
Facebook: https://www.facebook.com/dogado
Technischer Support: [email protected]
Supportsystem: http://support.dogado.de
Sitz der Gesellschaft: Dortmund Handelsregister: HRB 19737 Amtsgericht Dort=
mund,
Ust-IdNr: DE249338561 Gesch=E4ftsf=FChrer: Robin Tsch=F6pe, Timo Mankartz
Jelastic Cloud Hosting, machen Sie Ihre Webseite hochverf=FCgbar und skalie=
rbar!
Jetzt 14 Tage kostenlos und unverbindlich testen! Mehr unter : http://www.j=
elastic.de
--_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_
Content-Type: message/rfc822
Received: from DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by
DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) with Microsoft
SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:40 +0100
Received: from DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff]) by
DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff%14]) with mapi id
15.00.0775.031; Fri, 10 Jan 2014 10:45:40 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: base64
From: Peter Stutzinger <[email protected]>
To: "[email protected]" <[email protected]>
Subject: TNEF Testmail
Thread-Topic: TNEF Testmail
Thread-Index: Ac8N6LQ/yN5XQruBSFWwYuW7AIuW3g==
Date: Fri, 10 Jan 2014 10:45:39 +0100
Message-ID: <[email protected]>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
X-MS-Exchange-Organization-OriginalSize: 18165
X-MS-Exchange-Organization-OriginalArrivalTime: 10 Jan 2014 09:45:39.7572
(UTC)
X-MS-Exchange-Organization-MessageSource: StoreDriver
X-MS-Exchange-Organization-MessageDirectionality: Originating
X-MS-Exchange-Organization-Id: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Organization-AuthSource: DOX13BE01.hex2013.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-BCC:
X-MS-Exchange-Organization-OriginalClientIPAddress: 128.127.69.74
X-Originating-IP: [128.127.69.74]
X-MS-Exchange-Organization-OriginalServerIPAddress: fe80::4aa:2b19:10bb:b3ff%14
X-MS-Exchange-Organization-MessageLatency: SRV=DOX13BE01.hex2013.com:TOTAL=0
X-MS-Exchange-Organization-MessageLatency: SRV=DOX13BE01.hex2013.com:TOTAL=0
X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=DOX13BE01.hex2013.com:TOTAL=0;2014-01-10T09:45:40.757Z
X-MS-Exchange-Organization-Network-Message-Id: c0254cc7-4b09-4ea3-86cd-08d0dbffdba7
Return-Path: [email protected]
X-MS-Exchange-Forest-ArrivalHubServer: DOX13BE03.hex2013.com
X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: DOX13BE03.hex2013.com
X-MS-Exchange-Organization-HygienePolicy: Standard
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-Recipient-Limit-Verified: True
X-MS-Exchange-Organization-Transport-Properties: DeliveryPriority=Normal
X-MS-Exchange-Organization-Prioritization: 1
X-MS-Exchange-Organization-Rules-Execution-History: TransportVersioned.Hosting Transport
Restrictions%%%TransportVersioned.Disclaimer internal 970167
eJ8+ImZ1AQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEJgAEAIQAAADUwQ0Y0RUY3
AC8AcwBpAGcAbgBlAGQAAAAAAB8ADDoBAAAACgAAAEUAbgBVAHMAAAAAAOElDQo=
--_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_--

PDF to winmail.dat

When attaching a PDF file to email (outlook) the recieving file comes in as winmail.dat. Anyone know how to fix this? A real pain.

It came through fine originally from my work email which I have not changed the settings of in over 8 years. I viewed it properly at 6:54 am today as a PDF. I just went back to view it again 30 minutes ago and it was no longer a PDF but this new type. I had already received it so how could it be an issue with Outlook? Would tis not be an issue with iOS 8.1.3?

How to open winmail.dat attachments???

Hi, this is my first use of this discussion forum, so here goes: Can anyone tell me how to open attachments I am sent on a regular basis that are winmail.dat attachments???

Search Google for "winmail.dat mac" and you'll find many solutions
Also note that this forum is for troubleshooting Apple Software Update for Windows, a software package for Windows designed to update Apple products that run on Windows, and not related to your issue, so you should really post search/post your question in the Mac OS X forums

How to advoid Pdf attached files turning into winmail.dat file causing incovinience opening them? And why does the phone automatically changes the file???

The first time i opened the mail, the mail loaded the attactment as pdf file and i was able to open it without any problems. But then when i tried to open it again, i watched the phone automatically turned the pdf file into winmail.dat without any of my control. Since then, i werent able to open the file anymore! And this was lucky that i was able to see it as pdf file - all other attachments i have recieved since using my new ip6 all turn into winmail.dat
this is really incovinient and frustrating for work. i cant believe i cannot just open a pdf file as a pdf file on my ip6 in the emails i recieve. I was on ip4 before this and never have anything like this happened.
Solution needed asap please.
Thankyou!

Hi Jnkm,
I'm sorry to hear you are having issues with your new iPhone 6. If you are getting a winmail.dat file instead of a PDF, you may want to see if it may be the issue noted in the following article:
iPhone, iPad, or iPod touch does not display attachment in email - Apple Support
Regards,
- Brenden

MAC 2011 email attachments converted to winmail.dat

Hello Guys,
Does anyone encountered the same when MAC 2011 receives email with attachments the attachment becomes winmail.dat? What are things might causing it in the server level. Please advice.
NOTE: This is not affecting only one user but.
Thanks!
Uddan

Hi,
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.
To prevent or work around this issue, please refer to this similar thread
http://answers.microsoft.com/en-us/mac/forum/macoffice2011-macoutlook/excel-files-appear-as-winmaildat-in-outlook-2011/3159066f-5f40-4d59-a4bb-b79cd3bab743
KB: How to Prevent the Winmail.dat File from Being Sent to Internet Users
https://support.microsoft.com/en-us/kb/138053
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

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.

Winmail.dat Issues

Similar Messages

Maybe you are looking for