Looking for PowerObjects? Don’t worry, you’re in the right place! We’ve been part of HCL for several years, and we’ve now taken the final step in our acquisition journey: moving our website to the HCL domain. Nothing else is changing – we are still fanatically focused on Microsoft Business Applications!

PowerObjects Blog 

for Microsoft Business Applications


Emails Generated by Email Router Marked as spam from Dynamics CRM

Post Author: Joe D365 |

Imagine this scenario: After months of careful planning you generate your first email campaign from MSCRM. Many cool dashboards are ready to go to see who is reading which emails and which links are being clicked. Then as you click go, you watch with dismay as many of the emails start bouncing back one by one all marked as 'spam'. Welcome to the world of Internet email marking.

Fortunately with a properly configured smtp server and a couple other small items you can really increase the delivery rate. Here's our check list. Following these items should greatly increase delivery rates.

  1. MX Record. The server that is sending your emails should be listed in an mx record in dns.
  2. Reverse DNS. The server that is sending your emails should have a properly setup reverse dns. Check here: http://www.debouncer.com/reverse-dns-check
  3. Helo. Verify that your smtp server helo has the correct email server name and matches mx and reverse dns.
  4. SPF. If you don't already have an SPF record, be sure to create it. Here's more info: http://www.openspf.org/
  5. Unsubscribe. Always have an unsubscribe link in your newsletter. If you are already using our powerEmail component this is all set.
  6. Reputation. Ideally you want to send your newsletter from an email server that has been around for a while and has a good reputation.
  7. From Address. Have a valid from email address in a newsletter from the same domain.
  8. URL Links. If your newsletter contains many links have as many of them as possible from the same domain.
  9. EmailReg.Org. Register with www.emailReg.org.

Doing the above will cause many spam checking software to award 'points' for good setup. This is vital as emails generated from the crm email router are at a disadvantage since the email router breaks RFC2047 with by encoding part of the subject line. Unfortunately this is a Dot.Net framework issue and will not be fixed in the current email router.

If you looking for help with MSCRM or setting up you email router properly please get in touch with us at PowerObjects – we have a ton of experience with doing this for on premise or hosted implementations.

Have any other recommendations? We'd love to hear.

Happy CRM'ing!

Joe CRM
By Joe D365
Joe D365 is a Microsoft Dynamics 365 superhero who runs on pure Dynamics adrenaline. As the face of PowerObjects, Joe D365’s mission is to reveal innovative ways to use Dynamics 365 and bring the application to more businesses and organizations around the world.

5 comments on “Emails Generated by Email Router Marked as spam from Dynamics CRM”

    1. Hi Dan,

      If the email router is not being used, then your exchange server is the server sending out the emails. Yes - we'd still recommend these items for any mail server. The advantage is then that your subject line will not be breaking any RFCs, so doing these items should be up your acceptance level to very close to 100%.

  1. Hi,
    Must Reverse DNS match with same domain name or it just a reverse dns to other domain on same ip sufficient? If not, how to match reverse dns of multiple domains on 1 ip number?
    S.

    1. Hi,

      The reverse dns needs to match the full dns name of the email server. For example if your email server is mail.mycompany.com and its ehlo is mail.mycompany.com then reverse dns to that ip should also be mail.mycompany.com. Then mail server then can handle emails for any number of domains such as domaina.com, domainb.com and mycompany.com.

  2. We just started using the CRM 2011 e-mail router (UR 15) and are still having the issue where the subjects of outgoing e-mails are encoded. Do you know if the bug you describe will ever be fixed?

PowerObjects Recommends