E-mail Provider Base Classes
[Applies to: Microsoft Dynamics CRM 4.0]
The highest level base class is called EmailProvider, from which all e-mail provider classes derive. Intermediate (derived) classes provide additional behavior. For example, the PollingMailboxProvider implements a design pattern to connect to a mailbox that uses a configurable polling schedule. Out-of-box classes derived from EmailProvider correspond to actual e-mail providers. For example, the Pop3PollingMailboxProvider class implements POP3 e-mail processing.
The following diagram highlights the class hierarchy that is used to implement custom e-mail providers.
There are two ways that you can extend the object model to implement your own custom e-mail provider:
- Derive from an existing e-mail provider class and alter its behavior. For example, you may want to create a specialized POP3 e-mail provider that identifies certain keywords in the subject of processed e-mail messages, and creates alert records in Microsoft Dynamics CRM. In this case, starting an implementation from scratch could be expensive because you will have to implement the complete POP3 client protocol. By using a derived provider base class, some work is already handled for you.
- Create new e-mail providers to provide completely new functionality. For example, you may want to create an e-mail provider that downloads RSS feeds, and creates e-mail activities in Microsoft Dynamics CRM. In this case, deriving from existing e-mail providers might not be the best option because those classes do not have anything to do with RSS technology or protocols.
© 2010 Microsoft Corporation. All rights reserved.