|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
PidTagAttachTransportName 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 the name of an attachment file modified so that it can be associated with TNEF messages.
PR_ATTACH_TRANSPORT_NAME, PR_ATTACH_TRANSPORT_NAME_A, PR_ATTACH_TRANSPORT_NAME_W
TNEF and the transport provider use these properties. They are usually not available to client applications.
These properties are commonly used by TNEF when the underlying messaging system does not support the supplied filenames. For example, they are used when the user attaches multiple files with the same name, such as five files named CONFIG.SYS. The transport provider must modify the names to make sure they are unique. Each modified name appears in its attachment's PR_ATTACH_TRANSPORT_NAME and associated properties.