| Constant | Description | Data type | Property ID | Property Tag |
| PR_BODY | Contains the message text. | PT_TSTRING | 0x1000 | 0x1000001F |
| PR_BODY_W | Contains the message text. UNICODE compilation. | PT_UNICODE | 0x1000 | 0x1000001F |
| PR_BODY_A | Contains the message text. Non-UNICODE compilation. | PT_STRING8 | 0x1000 | 0x1000001E |
| PR_CE_SMS_RAW_BODY | Contains the binary portion of a RAW SMS message. This is contained in the pbBuffer parameter of the SmsReadMessage function. | PT_BINARY | 0x8132 | 0x81320102 |
| PR_CE_SMS_RAW_HEADER | Contains the header portion of a RAW SMS message. This is contained in RAW_PROVIDER_SPECIFIC_DATA::pbHeaderData, which is returned from the SmsReadMessage function in its pbProviderSpecificBuffer parameter. | PT_BINARY | 0x8131 | 0x81310102 |
| PR_REPORT_TEXT | Contains optional text for a report generated by the messaging system. | PT_TSTRING | 0x1001 | 0x1001001F |
| PR_REPORT_TEXT_W | Contains optional text for a report generated by the messaging system. UNICODE compilation. | PT_UNICODE | 0x1001 | 0x1001001F |
| PR_REPORT_TEXT_A | Contains optional text for a report generated by the messaging system. Non-UNICODE compilation. | PT_STRING8 | 0x1001 | 0x1001001E |
| PR_ORIGINATOR_AND_DL_EXPANSION_HISTORY | Contains information about a message originator and a distribution list expansion history. | PT_BINARY | 0x1002 | 0x10020102 |
| PR_REPORTING_DL_NAME | Contains the display name of a distribution list for which the messaging system is delivering a report. | PT_BINARY | 0x1003 | 0x10030102 |
| PR_REPORTING_MTA_CERTIFICATE | Contains an identifier for the message transfer agent that generated a report. | PT_BINARY | 0x1004 | 0x10040102 |
| PR_RTF_SYNC_BODY_CRC | Contains the cyclical redundancy check (CRC) computed for the message text. | PT_LONG | 0x1006 | 0x10060003 |
| PR_RTF_SYNC_BODY_COUNT | Contains a count of the significant characters of the message text. | PT_LONG | 0x1007 | 0x10070003 |
| PR_RTF_SYNC_BODY_TAG | Contains significant characters that appear at the beginning of the message text. | PT_TSTRING | 0x1008 | 0x1008001F |
| PR_RTF_SYNC_BODY_TAG_W | Contains significant characters that appear at the beginning of the message text. UNICODE compilation. | PT_UNICODE | 0x1008 | 0x1008001F |
| PR_RTF_SYNC_BODY_TAG_A | Contains significant characters that appear at the beginning of the message text. Non-UNICODE compilation. | PT_STRING8 | 0x1008 | 0x1008001E |
| PR_RTF_COMPRESSED | Contains the Rich Text Format version of the message text, usually in compressed form. | PT_BINARY | 0x1009 | 0x10090102 |
| PR_RTF_SYNC_PREFIX_COUNT | Contains a count of the ignorable characters that appear before the significant characters of the message. | PT_LONG | 0x1010 | 0x10100003 |
| PR_RTF_SYNC_TRAILING_COUNT | Contains a count of the ignorable characters that appear after the significant characters of the message. | PT_LONG | 0x1011 | 0x10110003 |
| PR_ORIGINALLY_INTENDED_RECIP_ENTRYID | Contains the entry identifier of the originally intended recipient of an auto-forwarded message. | PT_BINARY | 0x1012 | 0x10120102 |
| PR_BODY_HTML | Contains the Hypertext Markup Language (HTML)-encoded text body. | PT_TSTRING | 0x1013 | 0x1013001E |
| PR_BODY_HTML_W | Contains the HTML-encoded text body. UNICODE compilation. | PT_UNICODE | 0x1013 | 0x1013001F |
| PR_BODY_HTML_A | Contains the HTML-encoded text body. Non-UNICODE compilation. | PT_STRING8 | 0x1013 | 0x1013001E |
| PR_FLAG_STATUS | Contains the message's Outlook follow-up flags (NULL = no flag, 1 = Complete flag, and 2 = Active flag). | PT_LONG | 0x1090 | 0x10900003 |
| PR_FLAG_COMPLETE_TIME | Contains the date and time that the message was marked Complete. A property of type PT_SYSTIME has a FILETIME structure for its value | PT_SYSTIME | 0x1091 | 0x10910040 |
When a messaging transport downloads and saves HTML-formatted content, it uses one of two approaches:
- The transport stores MIME, and includes the HTML in the message MIME stream. Such HTML messages have a MIME part with "
Content-Type: text/html;" in the header. This approach applies to POP and IMAP, and is the approach taken by Microsoft for the built-in e-mail messaging transport.
- The transport stores body streams directly into messages, storing the non-Unicode HTML byte-stream into the PR_BODY_HTML_A message content property. This is the approach commonly used in custom transports.
When a transport opens a message from a message store, and makes the message available for a user to add content to it and then resend it, the HTML stream containing the user's new content is stored in the PR_BODY_HTML_A property.
When e-mail is composed on the mobile device, the PR_BODY_HTML and PR_BODY_HTML_W properties are typically left empty, and the byte-stream version of the HTML body is saved in PR_BODY_HTML_A.