In this webinar, our experts showcase a variety of demo use cases of how different components of the...
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.
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!
What if the CRM Router is not being used? Do these recommendations still apply?
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%.
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.
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.
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?