Transmitting and Copying Named Properties
Collapse the table of content
Expand the table of content
The document is archived and information here might be outdated

Transmitting and Copying Named Properties

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.

Whenever a named property is sent, moved, or copied, the name remains constant but the identifier must change to adhere to the mapping of the destination object. The only exception to this rule is when the source and destination have the same mapping signature, making remapping unnecessary.

It is the responsibility of the transport provider to remap the names of transmitted named properties to appropriate identifiers that work at the destination. The sending transport provider cannot know what the correct mapping is at the destination; it must transmit the names and rely on the receiving transport provider to map them to identifiers that work. The MAPI implementation of TNEF handles the remapping of named properties for transport providers. Transport providers can either handle the remapping manually or use the TNEF implementation.

A similar remapping of named properties must occur when these properties are copied between message stores. However, because message store providers can retrieve the name to identifier mapping of the destination, they can remap the properties right away and not have to rely on the destination message store.

© 2016 Microsoft