|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|
IMailUser : IMAPIProp
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.
Provides access to the many properties that are associated with messaging users. The IMailUser interface is implemented by messaging user objects. IMailUser inherits from the IMAPIProp : IUnknown interface and has no unique methods of its own.
Messaging user objects
Address book providers
This interface does not have any unique methods.
Five of the required properties are known as the base address properties for recipients:
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 MAPI Address Types.
Messaging users can display a collection of their properties by supporting the PR_DETAILS_TABLE (PidTagDetailsTable) property. PR_DETAILS_TABLE is a display table that describes the layout of a details dialog box or a tabbed property page that displays recipient property information. MAPI creates details dialog boxes when a client calls the IAddrBook::Details method.
Messaging user objects can have other optional properties associated with them. MAPI defines many properties that provide additional addressing information about a messaging user. All of these properties are character strings. The following list shows the more commonly used properties:
For a complete list of properties, see Mapping Canonical Property Names to MAPI Names.