Transport Neutral Encapsulation Format

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

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

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

Lua error in package.lua at line 80: module 'strict' not found. 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, this technique is not RFC-compliant because these messages have the following characteristics:

  • They may include non-ASCII characters outside the 0–127 US-ASCII range.
  • The lines in these messages are often too long for transport via SMTP.
  • They do not follow the CRLF.CRLF line termination semantics as specified in RFC 821.

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

Programs to decode and extract files from TNEF-encoded attachments are available on many platforms.

Multiplatform

Unix-like/POSIX command-line

  • yTNEF — GPL TNEF extractor from the POSIX command-line, designed specifically for reading winmail.dat
  • TNEF — GPL TNEF extractor from the POSIX command-line
  • KTNEF — GPL TNEF extractor for KDE

Mac

iPhone and iPad

Microsoft Windows

Android

Online

Software libraries

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Transport_Neutral_Encapsulation_Format&oldid=2825430"