| Platform SDK: MAPI |
The IMailUser interface is implemented by messaging user objects. IMailUser inherits from the IMAPIProp interface and has no unique methods of its own. The IMailUser interface provides access to the many properties that are associated with messaging users.
| Header file: | MAPIDEFS.H |
| Exposed by: | Messaging user objects |
| Implemented by: | Address book providers |
| Called by: | Client applications |
| Interface identifier: | IID_IMailUser |
| Pointer type: | LPMAILUSER |
| Transaction model: | Transacted |
No unique methods
| Required properties | Access |
|---|---|
| PR_ADDRTYPE | Read/write |
| PR_DISPLAY_NAME | Read/write |
| PR_DISPLAY_TYPE | Read-only |
| PR_EMAIL_ADDRESS | Read/write |
| PR_ENTRYID | Read-only |
| PR_OBJECT_TYPE | Read-only |
| PR_RECORD_KEY | Read-only |
| PR_SEARCH_KEY | Read-only |
Five of the required properties are known as the base address properties for recipients:
PR_ADDRTYPE
PR_DISPLAY_NAME
PR_EMAIL_ADDRESS
PR_ENTRYID
PR_SEARCH_KEY
These properties are considered special because many other groups of similar properties are built upon this base group. The other groups are used to describe a recipient in various roles, such as a message's original or delegate sender. For more information about these properties and how to use them, see Address Types.
Messaging users can display a collection of their properties by supporting the PR_DETAILS_TABLE property. PR_DETAILS_TABLE is a display table that describes the layout of a details dialog box — a tabbed property page dedicated to showing recipient property information. Details dialog boxes are created by MAPI when a client calls the IAddrBook::Details method.
Messaging user objects can have other optional properties associated with them. MAPI defines over forty properties that provide additional addressing information about a messaging user. All of these properties are character strings. The more commonly used properties are:
For a complete list of these properties, see Personal Information Properties.