Prevent your ASAP emails from being blocked

"Phishing" is the fraudulent practice of sending emails purporting to be from reputable companies in order to induce individuals to reveal personal information, such as passwords and credit card numbers. As more and more phishing scams are being circulated via email, email providers are becoming that much more aggressive in their efforts to block it.

This is a good thing, but it has also resulted in a higher percentage of legitimate email being mis-identified as forged and never making it to it's intended recipient. If you have had customers tell you that they're not receiving their ASAP emails, this may be why.

To address this ASAP is in the process of moving all of our email processing over to a service called Mandrill. Mandrill supports two email authentication systems know as DKIM (DomainKeys Identified Email) and SPF (Sender Policy Framework) that allow companies to verify that the emails they're sending are valid, which increases the odds of those emails being delivered.

However, in order to enable these authentication techniques you must first make a change to the account that hosts your domain name. The instructions for doing so are below. After you have completed the following steps you will then need to contact ASAP at support@asapconnected.com so we can verify that everything was done correctly. At that point we can switch your email over to Mandrill.

How to implement DKIM and SPF

DKIM and SPF need to be added to the server that hosts your domain name (godaddy, webgator, etc). Your host's customer support team can help you with this, or if you have a technical support person at your organization they can help as well. If they're unable to help we can set it up for you provided you provide us with access to your host account (please contact our team at support@asapconnected.com and include DKIM in the email somewhere).

 

To enable DKIM, create a TXT record for mandrill._domainkey.yourdomain.com (just replace yourdomain.com with the domain you're setting up) with the following value:
 
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
Some DNS providers require that semicolons be escaped. If your provider requires escaping, use this value instead:v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB\;
 
To enable SPF, if you don't yet have an SPF record, you'll want to add one for your domain. At a minimum, the value should be the following if you're only sending mail through Mandrill for that domain:v=spf1 include:spf.mandrillapp.com ?all
 
If you already have a TXT record with SPF information, you'll need to add Mandrill's servers to that record by adding include:spf.mandrillapp.com in the record (before the last operator, which is usually ?all, ~all, or -all).

 

Have more questions? Submit a request

Comments

Powered by Zendesk