This documentation is archived and is not being maintained.

MAPI Transport Provider Overview

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.

Transport providers handle message transmission and reception and implement security, if necessary. They also take care of any necessary preprocessing and postprocessing tasks. There is typically one transport provider for every active messaging system.

Client applications communicate with the transport provider through a message store provider.

Transport providers register with MAPI to handle one or more particular types of recipient entries. When a message is ready to be sent, MAPI must determine which transport provider should handle the transmission. Depending on the type of recipient, MAPI can even call upon more than one transport provider. If an unavailable transport provider is the only one that can handle the recipient, the message transmission will be postponed until a connection with that provider can be reestablished.

Some messaging systems are secure systems; all potential users are required to enter a set of valid credentials before access is permitted. MAPI prevents unauthorized access to such secure messaging systems by having the transport provider validate credentials at logon time.