Recipient Tables
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.
The recipient table contains information about all the recipients for a message. Message store providers implement recipient tables and client applications use them. Clients access a recipient table by making a call to the IMessage::GetRecipientTable method, or if the message store provider supports it, to the IMAPIProp::OpenProperty method. Clients access recipient tables with OpenProperty by specifying PR_MESSAGE_RECIPIENTS (PidTagMessageRecipients) for the property tag and IID_IMAPITable for the interface identifier. Changes to a recipient table can be made by calling the IMessage::ModifyRecipients method.
Recipient tables have a different column set depending on whether the message has been submitted. The following properties make up the required column set in recipient tables:
PR_DISPLAY_NAME (PidTagDisplayName)
PR_RECIPIENT_TYPE (PidTagRecipientType)
PR_ROWID (PidTagRowid)
The optional properties are:
PR_DISPLAY_TYPE (PidTagDisplayType)
PR_ENTRYID (PidTagEntryId)
PR_SPOOLER_STATUS (PidTagSpoolerStatus)
PR_OBJECT_TYPE (PidTagObjectType)
Submitted messages should include these additional properties in their required column set:
PR_ADDRTYPE (PidTagAddressType)
PR_RESPONSIBILITY (PidTagResponsibility)
Depending on a provider's implementation, additional columns, such as PR_SENDER_NAME (PidTagSenderName) and ENTRYID, might be in the table.
Any message store provider that supports message transmission — as indicated by the STORE_SUBMIT_OK bit being set in the provider's PR_STORE_SUPPORT_MASK (PidTagStoreSupportMask) property — should offer support for a particular set of restrictions in a recipient table implementation. The AND, OR, exist, and property restrictions are among the types of restrictions that should be available to recipient table users. Only the equal and not equal operators need to be supported on the property restriction. These restrictions must work with the following properties:
PR_ADDRTYPE
PR_EMAIL_ADDRESS (PidTagEmailAddress)
PR_RECIPIENT_TYPE
PR_RESPONSIBILITY
PR_SPOOLER_STATUS