Winmail.dat in reverse

When I send a mail to an Outlook user the attachment extension gets converted into .dat. Whether it is Word, Excel or whatever. If I send the email to another mac user and they forward it to an Outlook user the attachment is fine. This behaviour has happened under both Tiger and Leopard. Mac Mail is set to send attachments as Windows friendly. My default is to use plain text. It has not always had this behaviour, but just the last month or so. I am not aware of any software installed that might be having an impact other than the latest Apple updates that I always install.
Help!?!

The fact that another mac user can receive the message fine suggests the issue appears to be how outgoing data from your outgoing mail server is being handled when it is being received by the Outlook user's Incoming Mail server or the Outlook user's application/system.
http://docs.info.apple.com/article.html?artnum=304245
The send windows friendly attachment was designed to sent rich text file formatted documents using the encapsulated format for that feature included in Outlook. (For more information, click on the microsoft link, included on the linked page above.)
However, you are not sending any rich text format information if you are using plain text.
The mac user you are using to relay the information may not have Mail set the same as you.
Try sending plain text without windows friendly attachment checked or
send Rich Text attachments with windows friendly attachment checked.

Similar Messages

Outlook + TNEF, the reverse problem: outlook doesn't understand winmail.dat

A lot of information can be found about people with other mail clients not being able to read TNEF encoded (winmail.dat) messages, but I am having the opposite problem: *Outlook* can not read them anymore in our organization.
Mail servers are all Exchange 2010, Outlook versions 2010 and 2013.
Internal mails in TNEF/RTF format are fine.
In external mails coming in from the internet, if they arrive in TNEF, Outlook shows the plain ASCII text and the winmail.dat attachment.
The only thing I can find that may cause it, is a header inserted into the mail by our firewall. Now my question is, can that really be the reason?
Example snippet from an incoming mail with winmail.dat attachment, the "X-Watchguard-Antivirus" header is what I'm talking about.
--_000_B083931C9A44A84C8FF71C48801A6D5FACE1D820SRVMAIL1KSCCJHL_
Content-Dis; filename="winmail.dat"
Content-Transfer-Encoding: base64
Content-Type: application/ms-tnef; name="winmail.dat"
X-WatchGuard-AntiVirus: scanned 'winmail.dat'. clean action=allow
eJ8+IgAkAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEJgAEAIQAAAEEzQUExN0Y4
NDMwOEU3NDdCNkMxMzIyODkzRTRBRTg1ACUHAQ2ABAACAAAAAgACAAEFgAMADgAAAN8HAQAOAA0A
The "Content-disposition" line somehow got mangled when I quoted it above, the real line reads correctly "Content-Disposition colon attachment semicolon filename=...".

Hi,
The common reason that recipients receive emails as winmail.dat is that they are not using Outlook/Exchange, their email clients can't decipher the RTF/TNEF format thus the email is shown as winmail.dat.
In your scenario, you are using Outlook and Exchange, you should receive RTF emails correctly - It's proved with the Internal emails.
I can't be sure whether it's caused by the firewall, but if all external emails are facing this issue, it's most likely caused by the firewall.
To verify this, is it possible for you to configure the firewall not to insert the header? If it makes a difference to external emails that they can be read then, we can conclude the firewall was the culprit.
Regards,
Melon Chen
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

I can no longer open excel documents in my doc to go app. Error message simple reads can not open attachment. And the attachment is now a winmail.dat

I can no longer open excel documents in my doc to go app. Error message simple reads can not open attachment. And the attachment is now a winmail.dat

winmail.dat files usually mean the email has been sent in rich text format - you could either the person who sent it to send it in a different format e.g. plain text or HTML, or there are a few apps in the store that support it (search for winmail.date in the store).
winmail.dat files : http://support.apple.com/kb/TS1506

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.

Mail attachments come through as winmail.dat

When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files. Even if I perform a "save as" to the correct file name the file format is still not recognized. Why is this happening!?

Found the answer.
Hope it helps others
http://galaxycow.com/blogs/vermyndax/2008/01/12/winmaildat-hides-in-your-autocom plete/

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!

All attachments sent from work now only appear as winmail.dat

This didn't happen in the past and now if I send any type of attachment from work (png or zip for instance), the attachment only appears as a winmail.dat file on both my MacBook Pro running 10.7.3 and my iPhone running iOS5.1
The important thing here is the attachment is actually being set out correctly. I know this because if I pick it up using the web interface of my mail provider, the attachments are all present and correct.
Therefore the problem lies somewhere in iOS5.1 or OS10.7.3
Can anybody shed any light on this please?

Because when Outlook sends emails in Transport Neutral Encapsulation Format(TNEF), this is a Microsoft proprietary format. Hence, every other email program sees them as Winmail.dat.
In all versions of Outlook, you should be able to disable TNEF completely:
On the "Tools" menu, click "Options", and then click the "Mail Format" tab.
In the "Send in this message format" list, click "Plain Text" or "HTML", and then click "OK".
Have you tried that?

When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files. Even if I perform a "save as" to the correct file name the file format is still not recognized. Why is this happening!?

When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files. Even if I perform a "save as" to the correct file name the file format is still not recognized. Why is this happening!?

http://www.joshjacob.com/mac-development/tnef.php

New Due date for reversed Invoice

Hi Experts,
Can we determine a new due date for reversed invoice through standard configuration? The due date of reversed invoice remains the same as that of the original invoice even if its reversed after a year. It looks very odd that a FICA entry has a due date of past.
I tried by assigning the out-going payment term to the FICA payment term configuration but it doesnot determines a new due date from the posting date I provide during invoice reversal.
Any Clue ?
Regards
Satyajeet

Hi Satyajeet,
As per standard SAP, the due date of a particular invoice is derived from the date you are posting it in SAP and the payment terms configured in the contract account master, irrespective of the fact that whether it is a cancel-rebilled invoice or a normal invoice.
So if a invoice is posted on 05.08.2011 and the payment terms mantained at the CA master is 5 days then the due date will be on 10.08.2011.
The due date of a invoice is determined in event R417. Check if any custom FM is assigned in there which is changing the standard SAP functionality.
Also check event 1330, which gets called from event R417 to determine the due date.
Hope it helps.....
Thanks,
Amlan

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

Winmail.dat : problems after iOS5 update...

Folks... After updating to iOS5, I am finding that any JPG or pasted picture sent to me in e-mail does NOT appear on my iPhone4. It is NOT simply a Microsoft problem, as is always stated.
If I start a mail (HTML) in Outlook, and paste an Image, and send it to my iPhone's Comcast Account, I get the winmail.dat attachment
If I start a mail (HTML) in Outlook, and paste and Image, and send it to my iPhone's Gmail account, it is read just fine and the image appears. I have also copied my Comcast account, just to ensure the same mail.... and get the same winmail.dat result with my comcast account.
If I look at my Comcast mail account, in Outlook (Desktop), and online --- the same image is received fine and the image appears. The only place is does NOT appear is on the phone.
This seems to have something to do with how the iPhone interprets mail FROM Outlook. There has HAD to have been a change in how this works, because it used to work just fine.
Someone at Apple: I would appreciate a response on this. It is very frustrating, and all signs are that it is an iOS5 thing.
thanks
Brandon

I did a little more searching, and found this solution on another Apple forum. It worked beautifully. It makes no sense, but who cares? It was easy and effective.
Hope it helps!
Yes, I did try that.
However I have now found the answer:
http://galaxycow.com/blogs/vermyndax/2008/01/12/winmaildat-hides-in-your-autocom plete/
Once the entry for my home address was removed from the Autocomplete drop down list, everything went back to normal.

How do you open a PDF that comes in as a winmail.dat on an iPad2

How do you open a PDF file that comes in as winmail.daton an iPad2? Is there any setting that I need to turn on? Or do i need to purchase a converter to make this work?
Thanks,
firehorse7

You could ask whoever sent it to you to resend the email, but not in rich text format : http://support.apple.com/kb/TS1506
Otherwise there are a number of apps in the store that say that they support winmail.dat (search for 'winmail.dat')

How do I view a document sent to me in Winmail.dat(2.0MB). I have downloaded and installed the libero app butthis doesn't help me open the winmail.dat document. Help very much appreciated. THANKS JANE

How do I view a document sent to me in Winmail.dat(2.0MB). I have downloaded and installed the libero app but this doesn't help me open the winmail.dat document. Help very much appreciated. THANKS JANE

http://www.creativeinaustria.com/LetterOpenerPro?utm_source=macupdate.com&utm_me dium=referral&utm_campaign=Distribution%2BChannels
Try it
http://www.macupdate.com/app/mac/22614/letter-opener
http://www.creativeinaustria.com/LetterOpenerLite

How do i open winmail.dat attachments in mail

How do i open winmail.dat attachments in mail ?

Having problems with Winmail.dat attachments? This is really Windows problem but their hubris will not allow them to admit it.
Windows does have a global fix for this problem but it is not a general patch - in their KB there is a fix for Exchange servers which cause the winmail.dat problem but most users don't know about it or have it implemented.
http://support.microsoft.com/kb/138053http://
Here is a solution that Apple users can get for $30. An Austrian program and APP called Letter Opener http://www.creativeinaustria.com/http:// is the solution to seamlessly opening Winmail.dat files.

TS3276 Most attachments from a specific address (work) can not be opened, identified as winmail.data and no data available. Not sure if this is based on the e-mail coming from a windows based system, too old of a windows based system or simply how i have

Most attachments from a specific address (work) can not be opened, identified as winmail.data and no data available. Not sure if this is based on the e-mail coming from a windows based system, too old of a windows based system or simply how i have it set on my Mac.

Brightbleu wrote:
Most attachments from a specific address (work) can not be opened, identified as winmail.data and no data available. Not sure if this is based on the e-mail coming from a windows based system, too old of a windows based system or simply how i have it set on my Mac.
Winmail.data are not usable files. They just preserve RTF within the message.
http://support.microsoft.com/kb/278061
Cheers
Pete

Winmail.dat in reverse

Similar Messages

Maybe you are looking for