Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

PidTagTnefCorrelationKey Canonical Property

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Contains a value that correlates a Transport Neutral Encapsulation Format (TNEF) attachment with a message.

Associated properties:

PR_TNEF_CORRELATION_KEY

Identifier:

0x007F

Data type:

PT_BINARY

Area:

MAPI envelope

It is recommended that TNEF attachment sub-objects expose this property. This property determines whether or not an inbound TNEF file belongs to the message it is attached to. It is used primarily by transport providers and gateways.

On an outbound message, the transport provider should compute a binary value unique to that message, or use an existing value that satisfies the uniqueness requirement, such as a message identifier. The transport provider should store this value in this property and then call the ITnef::AddProps method to encapsulate it. The same value should also be stored in the transport envelope in a place defined by the provider, such as the message header.

On an inbound message, the transport provider should call the ITnef::ExtractProps method to decapsulate the TNEF attachment and then compare this property with the value stored in the transport envelope. If the values match, TNEF should be processed normally, that is, all the properties extracted from the TNEF attachment should be used. If the values do not match, all the properties from the TNEF attachment should be ignored. If this property is not set, the TNEF file should be considered to belong to this message, and the other properties extracted from it should be used.

Protocol Specifications

[MS-OXPROPS]

Provides references to related Exchange Server protocol specifications.

[MS-OXCFXICS]

Handles the order and flow for data transfers between a client and server.

[MS-OXCMAIL]

Converts from Internet standard e-mail conventions to message objects.

[MS-OXTNEF]

Encodes and decodes message and attachment objects to an efficient stream representation.

Header Files

Mapidefs.h

Provides data type definitions.

Mapitags.h

Contains definitions of properties listed as alternate names.

Show:
© 2014 Microsoft