Share via

MAPI Properties

  • Article

Send Feedback

This section contains property tag definitions for standard properties of Windows Mobile-based Messaging API (MAPI) objects. Each property has an associated hexadecimal Property Identifier (ID). Properties within similar categories are grouped together into ranges of Property IDs.

**Note   **Unlike members of COM variant arrays, every member in a MAPI multivalued property array is of the same type. Conversation ID is not implemented. (Message grouping by thread is not supported.) There is no provision in Windows Mobile-based MAPI for iterating through an item's properties. Instead, you must retrieve one property at a time.

In This Section

The following subsections correspond to each of the property types, and are listed according to their position in the range of Property IDs. See the remarks section for more information.

  • Message Envelope Properties
    Message object properties, such as PR_MESSAGE_CLASS, PR_SUBJECT, and PR_CONVERSATION_TOPIC. There are 189 of them in total.
  • Message Content Properties
    Message content properties, such as PR_BODY, PR_REPORT_TEXT, and PR_RTF_COMPRESSED. There are 18 of them in total.
  • Message Recipient Properties
    Message recipient properties, such as PR_SENDER_NAME, PR_SENDER_EMAIL_ADDRESS, and PR_NON_RECEIPT_NOTIFICATION_REQUESTED. There are 42 of them in total.
  • Non-Transmittable Message Properties
    Non-transmittable message object properties, such as PR_DELETE_AFTER_SUBMIT, PR_DISPLAY_BCC, and PR_MESSAGE_DELIVERY_TIME. There are 45 of them in total.
  • Common Non-Transmittable Properties
    Non-transmittable properties that never appear on message objects., such as PR_ENTRYID, PR_OBJECT_TYPE, and PR_ICON. There are 12 of them in total.
  • Common Transmittable Properties
    Transmittable properties that never appear on message objects., such as PR_DISPLAY_NAME, PR_EMAIL_ADDRESS, and PR_CREATION_TIME. There are 26 of them in total.
  • MAPI Form Properties
    Properties that appear on message form objects, such as PR_FORM_VERSION, PR_FORM_CLSID, and PR_FORM_MESSAGE_BEHAVIOR. There are 20 of them in total.
  • Message Store Properties
    Properties that appear on message store objects, such as PR_DEFAULT_STORE, PR_STORE_STATE, and PR_MDB_PROVIDER. There are 17 of them in total.
  • Folder and Address Book Container Properties
    Properties that appear on folder and address book container objects, such as PR_FOLDER_TYPE, PR_CONTENT_COUNT, and PR_AB_PROVIDER_ID. There are 26 of them in total.
  • Attachment Properties
    Properties that appear on attachment objects, such as PR_ATTACH_EXTENSION, PR_ATTACH_FILENAME, and PR_ATTACH_ADDITIONAL_INFO. There are 30 of them in total.
  • Address Book Properties
    Properties that appear on address book objects, such as PR_DISPLAY_TYPE, PR_TEMPLATEID, and PR_PRIMARY_CAPABILITY. There are 3 of them in total.
  • Mail User Properties
    Recipient properties, such as PR_GIVEN_NAME, PR_STREET_ADDRESS, and PR_CONTACT_EMAIL_ADDRESSES. There are 261 of them in total.
  • User Profile Properties
    Account profile properties, such as PR_PROFILE_NAME, PR_DEFAULT_PROFILE, and PR_SERVICES. There are 28 of them in total.
  • Status Object Properties
    Session resource properties, such as PR_STATUS_CODE, PR_STATUS_STRING, and PR_RESOURCE_METHODS. There are 22 of them in total.
  • Display Table Properties
    Display table properties, such as PR_CONTROL_TYPE, PR_CONTROL_ID, and PR_XPOS. There are 9 of them in total.
  • Windows Mobile Defined MAPI Properties
    Custom properties defined for MAPI running on the Windows Mobile Platform, such as PR_CE_TRANSPORT_NAME, PR_CE_SIGNATURE, and PR_CE_INCOMING_SERVER. There are 38 of them in total.

Remarks

Conversation ID is not implemented. (Message grouping by thread is not supported.) There is no provision in Windows Mobile-based MAPI for iterating through an item's properties. Instead, you must retrieve one property at a time.

The following table shows the set of Property ID ranges.

From To Category
0000   Reserved by MAPI for the special value PR_NULL.
0001 0BFF Message envelope properties defined by MAPI.
0C00 0DFF Recipient properties defined by MAPI.
0E00 0FFF Non-transmittable message properties defined by MAPI.
1000 2FFF Message content properties defined by MAPI.
3000 3FFF Properties for objects other than messages and recipients defined by MAPI.
4000 57FF Message envelope properties defined by transport providers.
5800 5FFF Recipient properties defined by transport and address book providers.
6000 65FF Non-transmittable message properties defined by clients.
6600 67FF Non-transmittable properties defined by a service provider. These properties can be visible or invisible to users.
6800 7BFF Message content properties for custom message classes defined by creators of those classes.
7C00 7FFF Non-transmittable properties for custom message classes defined by creators of those classes.
8000 FFFE Properties defined by clients and occasionally service providers that are identified by name through the IMAPIProp::GetIDsFromNames method.

Property IDs for objects other than messages and recipients fall in the Property ID range from 0x3000 through 0x3FFF. The following table shows how this range is further subdivided into smaller ranges to make assigning new Property IDs easier.

From To Category
3000 32FF Common properties that appear on multiple objects, such as PR_DISPLAY_NAME and PR_ENTRYID.
3200 33FF Form properties.
3400 35FF Message store properties.
3600 36FF Folder and address book container properties.
3700 38FF Attachment properties.
3900 39FF Address book properties.
3A00 3BFF Messaging user properties.
3C00 3CFF Distribution list properties.
3D00 3DFF Profile properties.
3E00 3FFF Status object properties.

Secure Property ID Range

Constant Property ID
PROP_ID_SECURE_MIN 0x67F0
PROP_ID_SECURE_MAX 0x67FF
  • SPropValue
    Contains information on property tag types.

See Also

Messaging | MAPI Data Types | MAPI Enumerations | MAPI Functions | MAPI Interfaces | MAPI Macros | MAPI Structures

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.