[Applies to: Microsoft Dynamics CRM 4.0]
Find the latest SDK documentation: CRM 2015 SDK
An e-mail provider is a pluggable component that is integrated with the Microsoft Dynamics CRM E-mail Router service. The provider is responsible for specialized e-mail processing and interfacing with an e-mail protocol. The E-mail Router manages the routing of e-mail to or from the Microsoft Dynamics CRM platform. The E-mail Router is supported by on-premise, Internet-facing, hosted, and Online versions of Microsoft Dynamics CRM.
The Microsoft Dynamics CRM E-mail Router includes different e-mail providers, each implementing a particular e-mail protocol. For example, the POP3 e-mail provider examines e-mail messages that are received by a POP3 mailbox and calls into Microsoft Dynamics CRM to create e-mail activities. The SMTP e-mail provider connects to Microsoft Dynamics CRM to download e-mail activities waiting to be sent, composes the e-mail messages, and submits the e-mail messages to an SMTP server.
For each type of e-mail provider, several instances of the provider may be executing at the same time. For example, at a given time, five instances of the POP3 e-mail provider may be running, each processing e-mail messages from one mailbox and delivering e-mail to a different organization.
In addition, the platform supports the integration of custom e-mail providers to the E-mail Router service in order to extend or customize the e-mail handling functionality of Microsoft Dynamics CRM. An extensible framework based on the concept of e-mail providers and XML files is provided to develop custom providers. This e-mail provider documentation explains how you can extend the object model to build your own highly specialized e-mail provider.
From a design perspective, each type of e-mail provider should accept configuration parameters. Two examples of configuration parameters are name of the mailbox to connect to and name of the e-mail server to connect to. Some e-mail providers may also have to persist run-time state information. For example, a provider might need persistent values for the time stamp of the last processed message or number of e-mail messages processed to this point. Such state information should not be lost if the E-mail Router service is restarted.
The following sections describe how to extend the functionality of the Microsoft Dynamics CRM E-mail Router through the development of custom e-mail providers.
In this Section
Describes important E-mail Provider classes.
Describes how to develop a custom e-mail provider.
Describes how to deploy and debug a custom e-mail provider.