#DOWNLOAD WINMAIL WINDOWS 10 HOW TO#
#DOWNLOAD WINMAIL WINDOWS 10 SOFTWARE#
#DOWNLOAD WINMAIL WINDOWS 10 WINDOWS#

#DOWNLOAD WINMAIL WINDOWS 10 HOW TO#

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.įrom Microsoft: How to Prevent the Winmail.dat File from Being Sent to Internet Users. (Most clients simply treat these winmail.dat files as an arbitrary attachment on the message.) Like many other mail clients, the iOS mail client does not decode, process nor create these winmail.dat files. 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.

#DOWNLOAD WINMAIL WINDOWS 10 WINDOWS#

The winmail.dat is a Windows Mail data file, after all. 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. This is a Microsoft Windows setting with Microsoft Outlook or within the Exchange Server gateway in general. 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. Phone A to Phone B correct format is received. If done from Phone B to Phone A, Phone A winmail.dat persists. Even if I use Phone A to send to the other account on Phone A, winmail.dat is received. I took it a step further and used the phones to test sending. Phone B always receives the attachment in it's correct format. Phone A always receives a winmail.dat file no matter which client or email address is used. So basically I used two different clients each time sending to four addresses two are located on each phone. I used Gmail as an alternate mail client with the same result. This is where the confusion arose since one phone receives fine and the other doesn't. I created one email per setting and addressed to both people on their corporate exchange account (same server for both) and their gmail accounts. In Outlook, I changed the setting for how the mail sent to each typoe to resolve the issue. As an alternative test, try using Thunderbird or another mail client, and see if sending mail to the addresses works as expected.

#DOWNLOAD WINMAIL WINDOWS 10 SOFTWARE#

If your tests are sending to different email addresses to reach those two phones, there's the trigger - the settings for the two addresses differ in the Microsoft Windows software you're working with. This choice uses the sender's settings for the receiving email address. It's all on the sending application.įor your reported behavior, a re the messages to both phones using the exact same target email address? Because that's how the Windows mail client makes this determination on whether or not to send a Windows-format mail message. With this case, it is the sender and the sending program chooses whether to send HTML or text format messages, or WINMAIL.DAT files, and that's the key detail here. Not having support for the Microsoft Windows winmail.dat message format, you'll just get an attachment that's not viewable. IPhone doesn't know from the winmail.dat files, it just receives and (tries to) display whatever was sent. In all cases, one received the attachments fine and the other didn't. Emails were sent to test from Outlook in all three available formats (RTF, Text, HTML) and also from Gmail. One receives the images and attachments fine.

In my case this appears to be a phone issue.

Download winmail windows 10