E-mail Router Configuration

The CRM E-mail Router configuration can be challenging to setup for many people.  The Dynamics Forum contains many posts from people who are having various challenges implementing and configuring the E-mail Router so I thought I would write about the configurations I have used that work when ‘standard’ configuration does not always work as expected.
The E-mail Router Implementation guide provides the detail required to implement the E-mail Router in various environments to include configuring for use with Exchange and Pop3.  You can also find a wealth of information about deploying and configuring the CRM E-mail Router in the Dynamics Resource Center.
Here is some additional information that you might find helpful if you are experiencing challenges getting things to work as expected in an Exchange environment:
  • You can install the E-mail Router on any machine in the network except the Exchange Server machine
  • If you installed the E-mail Router on the Exchange Server machine, uninstall it and re-install on a different machine
  • Unexpected issues that are challenging to troubleshoot generally occur if you install the e-mail router on the same machine as the Exchange server so avoid it
  • If your IT department allows, create an Active Directory user with a name like CRMMail@YourOrg.com with a mailbox and give that user Domain Admin rights
  • You can use this user for the Forward e-mail account if you are configuring a Forward E-mailbox
  • When you install the E-mail Router, the installation will deploy an E-mail Router Service which you can find under Services.
  • Open the E-mail Router Service and change the Logon Account to the CRMMail user or another Domain Admin user. 
  • This will ensure that the service does not encounter any unexpected Network access issues
After you have install the E-mail router, you will open the E-mail Router Configuration Manager and follow the steps in the Implementation Guide.  You will configure Incoming, Outgoing, and Deployment settings.  Below are the settings that I found work most consistently:
Profile Name = Whatever you prefer
E-mail Server = Exchange
Authentication = Windows Authentication
Location = Type the HTTP-DAV location of the Microsoft Exchange server (this is typically your OWA URL ending with .com)
Access Credentials = Other Specified (CRMMail or other Domain User name and password)
Profile Name = Whatever you prefer
E-mail Server Type = SMTP
Authentication Type = Windows Authentication
Location – Server = ExchangeServerName (do not include URL, .com or anything other than the name of the Exchange Server)
Access Credentials = Other Specified (CRMMail or other Domain User name and password)
Deployment = Make the appropriate selection depending on your environment (My Company or Online Service Provider)
Access Credentials = Other Specified (CRMMail or other Domain User name and password)
Select the Default Configurations from the drop down
More often than not, the one key item that I found to get things to work when they are not working as expected is setting the E-mail Router Service, and the Incoming, Outgoing, and Deployment Access Credentials to a Domain Admin user account.
If you are implementing the E-mail Router with Pop 3 and a Support Queue then Michael Lu has a very good video tutorial that will help. 

One comment

  1. Hey! I could have sworn I’ve been to this website before but after reading through some of the post I realized it’s new to me.
    Nonetheless, I’m definitely happy I found it and I’ll be bookmarking and checking back frequently!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s