Winmail.dat files are TNEF’s. Transport Neutral Encapsulation Format attachment files which allow Microsoft Outlook users to receive email messages which retain the original formatting. Those files are much hated among the Mac community but there’s a way out. For Better Or For Worse. Jump to Opening a Winmail.dat or ATT0001.dat File - Open the email with the attachment. Winmail.dat and ATT0001.dat files are.
![]()
Ajlayne wrote:In my case this appears to be a phone issue. I have two iPhone 5's.
One receives the images and attachments fine. The other doesn't. Both are on the same version of the OS.
![]()
Emails were sent to test from Outlook in all three available formats (RTF, Text, HTML) and also from Gmail. In all cases, one received the attachments fine and the other didn't.iPhone doesn't know from the winmail.dat files, it just receives and (tries to) display whatever was sent. Not having support for the Microsoft Windows winmail.dat message format, you'll just get an attachment that's not viewable. 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. It's all on the sending application.For 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. This choice uses the sender's settings for the receiving email address. 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. As an alternative test, try using Thunderbird or another mail client, and see if sending mail to the addresses works as expected. 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.
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:.
In short, either the Outlook client settings or the Exchange Server (IMC) settings will need to be changed here. Hoffman,Thank you for trying. This is quite frustrating.I must be missing something she receives attachments this way from all senders to all three of her email accounts on her iPhone.
If she opens it at the computer or on her iPad the attachments are fine. It's only on her iPhone. Also, out of 60+ people in my office, she's the only one with the issue.
We don't have access to the exchange server and Outlook settings have been changed per the above several times before and after I posted. This person receives hundreds of emails and I find it hard to believe that every sender is using an Exchange server with the wrong settings or that Gmail's settings are wrong.
Sending her to the Apple store for help. She most likely clicked or deleted something on the phone that caused this. Compare the settings of the iPad and the iPhone devices — wondering if the 'computer' referenced here is actually a Microsoft Windows computer running the Microsoft Outlook, Outlook Express tool or some other Microsoft mail client, and thus likely to respond correctly to receiving a winmail.dat file — and particularly if the two iOS devices are configured differently; one configured to SMTP (and POP or IMAP) and one configured to Microsoft Exchange.
If the two iOS devices are consistent and/or configured for SMTP (and POP or IMAP), then there's something really weird with the sending client or sending mail server, or there are different email addresses. Apple Footer.This site contains user submitted content, comments and opinions and is for informational purposes only.
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
(Redirected from Winmail.dat)
Transport Neutral Encapsulation Format or TNEF is a proprietary email attachment format used by Microsoft Outlook and Microsoft Exchange Server. An attached file with TNEF encoding is most often named winmail.dat or win.dat, and has a MIME type of Application/MS-TNEF.The official (IANA) media type, however, is application/vnd.ms-tnef.[1]
Overview[edit]
Some TNEF files contain information used by only Outlook to generate a richly formatted view of the message, such as embedded (OLE) documents or Outlook-specific features such as forms, voting buttons, and meeting requests. Other TNEF files may contain files which have been attached to an e-mail message.
Within the Outlook e-mail client, TNEF encoding cannot be explicitly enabled or disabled (except via a registry setting[2]). Selecting RTF as the format for sending an e-mail implicitly enables TNEF encoding, using it in preference to the more common and widely compatible MIME standard. When sending plain text or HTML format messages, some versions of Outlook (apparently including Outlook 2000[3]) prefer MIME, but may still use TNEF under some circumstances (for example, if an Outlook feature requires it).[3][4]
TNEF attachments can contain security-sensitive information such as user login name and file paths,[3][4] from which access controls could possibly be inferred.
Exchange Server[edit]
Native-mode Microsoft Exchange 2000 organizations will, in some circumstances, send entire messages as TNEF-encoded raw binary independent of what is advertised by the receiving SMTP server. As documented in Microsoft KBA #323483,[5] this technique is not RFC-compliant because these messages have the following characteristics:
Internal communications between Exchange Servers (2000 and later) over SMTP encode the message in S/TNEF (Summary TNEF) format. The conversion between the format needed by the end client on the Internet is performed on the last Hub Transport server before final delivery, and when the Hub Transport role of an Exchange Server is about to deliver the message to a mailbox role server, the message is converted to MAPI format for storage.
S/TNEF differs from TNEF in that it is 8-bit (not 7-bit for TNEF) and does not contain a plain-text portion.
Decoding[edit]
Programs to decode and extract files from TNEF-encoded attachments are available on many platforms.
Multiplatform[edit]
Unix-like or POSIX command-line[edit]
Mac[edit]
iPhone and iPad[edit]
Microsoft Windows[edit]
Android[edit]
Online[edit]
Software libraries[edit]
References[edit]
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Transport_Neutral_Encapsulation_Format&oldid=918710338'
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |