The PR_ATTACH_TRANSPORT_NAME property contains the name of an attachment file modified so that it can be correlated with TNEF messages.
| Header file: | MAPITAGS.H |
| May be exposed by: | Attachment subobjects |
| Identifier: | 0x370C |
| Property type: | PT_TSTRING |
| Property tag: | 0x370C001E (0x370C001F for Unicode) |
TNEF and the transport provider use the PR_ATTACH_TRANSPORT_NAME property. It is usually not available to client applications.
This property is commonly used by TNEF when the underlying messaging system doesn't support the supplied filenames. For example, PR_ATTACH_TRANSPORT_NAME is 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 ensure uniqueness. Each modified name appears in its attachment's PR_ATTACH_TRANSPORT_NAME property.
MAPI works only with filenames, and other strings passed to it, in the ANSI character set. Applications that use filenames in an OEM character set must convert them to ANSI before calling MAPI.