|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|
PidTagMessageStatus 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 a 32-bit bitmask of flags that defines the status of a message in a contents table.
A message can exist in a contents table and in one or more search-results tables, and each instance of the message can have a different status. This property should not be considered a property on a message but a column in a contents table.
A client application can set one or more of the following flags in this property:
The MSGSTATUS_DELMARKED, MSGSTATUS_HIDDEN, MSGSTATUS_HIGHLIGHTED, and MSGSTATUS_TAGGED flags are defined by the client. Transport and store providers pass these bits without any action.
Clients can interpret these values in any way that is appropriate for their applications. One way that many clients use this property is to display messages marked for deletion with a representative icon.
A remote viewer client can set MSGSTATUS_REMOTE_DELETE or MSGSTATUS_REMOTE_DOWNLOAD on messages in the header folder presented to it by the remote transport provider. The client application can examine each message header in this folder to determine whether the message should be downloaded or deleted at the remote message store. It then uses the IMAPIFolder::SetMessageStatus method to set the appropriate flag. SetMessageStatus is the only way to set any of the flags in this property; the IMAPIProp::SetProps method cannot be used. To retrieve this property, clients call IMAPIFolder::GetMessageStatus rather than IMAPIProp::GetProps.
Bits 16 through 31 (0x10000 through 0x80000000) of this property are available for use by the interpersonal message (IPM) client application. All other bits are reserved for use by MAPI; those not defined in the preceding table should be initially set to zero and not altered subsequently.