PidTagAttachLongPathname 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 an attachment's fully-qualified long path and filename.
Associated properties: |
PR_ATTACH_LONG_PATHNAME, PR_ATTACH_LONG_PATHNAME_A, PR_ATTACH_LONG_PATHNAME_W |
Identifier: |
0x370D |
Data type: |
PT_STRING8, PT_UNICODE |
Area: |
Message attachment |
Remarks
These properties are applicable when you use any of the PR_ATTACH_METHOD (PidTagAttachMethod) property's values that indicate attachment by reference: ATTACH_BY_REFERENCE, ATTACH_BY_REF_RESOLVE, or ATTACH_BY_REF_ONLY. Platforms that support long filenames should set both PR_ATTACH_LONG_PATHNAME or associated properties and PR_ATTACH_PATHNAME (PidTagAttachPathname) properties when sending, and should check PR_ATTACH_LONG_PATHNAME or associated properties first when receiving.
The client application should set these properties to a suggested long path and filename to be used if the host machine receiving a message supports long filenames. Setting these properties indicates that the attachment data is not included with the message but is available on a common file server.
Unlike the directories and filenames provided by PR_ATTACH_PATHNAME, these directories and filenames are not restricted to an eight-character directory or filename plus three-character extension. Instead, each directory or filename can be up to 256 characters long, including the name, extension, and separator period. However, the overall path is limited to 256 characters.
Clients should use a universal naming convention (UNC) in most cases when the file is shared, and should use an absolute path when the file is local.
MAPI works only with paths and filenames in the ANSI character set. Client applications that use paths and filenames in an OEM character set must convert them to ANSI before calling MAPI.
Related Resources
Protocol Specifications
[MS-OXCMSG]
Handles message and attachment objects.[MS-OXORMMS]
Specifies the properties of rights-managed encoded messages.
Header Files
Mapidefs.h
Provides data type definitions.Mapitags.h
Contains definitions of properties listed as alternate names.