Transport Neutral Encoding Format

Transport Neutral Encoding Format

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Transport Neutral Encoding Format (TNEF) provides a standard method for passing both textual and binary message data. In this method, TNEF encapsulates MAPI properties not supported by an underlying messaging system into a binary stream that can accompany a message through transports and gateways. The target transport can then decode the encapsulation to retrieve all the properties of the original message.

Because a message consists of MAPI properties, your gateway can use TNEF to encapsulate the message properties into a binary stream. This stream can then be attached to an outbound message for transfer by the gateway. A gateway must be able to determine whether an attachment is a TNEF attachment.

You can use TNEF when you want to create extra MAPI properties (for example, in a custom message class) and put these extra properties into an attachment. You can also attach multiple messages to each other in a form that the foreign system understands. Using TNEF enables you to transmit messages with more complex formats, such as Rich Text Format (RTF).

Note  In versions of Exchange Server 2003 earlier than Exchange Server 2003 SP2, recurring meeting requests or updates encoded as Rich Text Format (RTF) can lose the recurrence information. With Exchange Server 2003 SP2, recurrence information encoded as RTF is no longer deleted and your applications can successfully send recurring meeting requests encoded as RTF.

Before you map addresses, determine whether any of the Responsibility-TRUE recipients are TNEF recipients. The Boolean MAPI property PR_SEND_RICH_INFO indicates whether the recipients can use TNEF. Send all TNEF recipients a separate message containing the TNEF attachment.

Note  Do not include reports in TNEF attachments.

TNEF attachments can be included in or excluded from the TNEF stream. Excluded attachments must have unique names. TNEF generates a tagged form of the message text that is used on inbound processing to recover attachment positions.

For more information about TNEF, see MAPI Programmer's Reference .

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

This topic last updated: July 2006

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.