Authenticating Elastic Email Emails with SPF and DKIM

Why are my Elastic Email emails going to Spam?

If you have a problem with Elastic Email emails going to spam, that is, going to the junk folder of your recipients, then it is very likely an issue with your email authentication. Emails failing authentication, be they failing SPF, failing DKIM, or failing DMARC is common, as SPF, DKIM, and DMARC are often not properly implemented by domain administrators. Often, the main cause of Elastic Email emails being blocked is due to the Elastic Email emails failing DMARC, which in the case of Elastic Email, is usually due to a misconfiguration of SPF and DKIM.

How to stop Elastic Email emails going to Junk.

The first step to preventing Elastic Email email going to spam is to retrieve a failed message and access its header information. This will allow you to quickly diagnose whether any authentication issues such as DKIM or DMARC are flagging your email as spam, instructing the recipient sender to move it to junk. Simply paste the email headers into our free Stellastra Deliverability Tool, which you can use freely with no log in required. Our deliverability tool should allow you to avoid Elastic Email emails from going to spam, or at least rule out authentication as the issue.

How to remove ‘via elasticemail.com’ or ‘on behalf of elasticemail.com’

Another example of where a Elastic Email DKIM misconfiguration is to blame, is if your recipients report seeing the message as ‘via elasticemail.com’ or ‘on behalf of elasticemail.com’ and that the emails typically end up in spam or junk. The Stellastra Email Deliverability tool above will confirm this prognosis, however, you may also wish to configure DKIM for Elastic Email by logging in to your Elastic Email account to check to see if you have followed the following article to configure your Elastic Email dkim setup to authenticate your domain.

How to stop Elastic Email Failing DMARC

To ensure that your Elastic Email campaigns pass DMARC and get delivered to your prospects, it is important to ensure that DKIM and SPF passes authentication for your domain. A common mistake is to sign an email with Elastic Email’s own DKIM keys. However, in order for Elastic Email’s email to pass authentication for your own domain, it is necessary to use your own DKIM keys as per Elastic Email’s own guide. If you wish to verify the above, paste the message headers for a failed Elastic Email message into our Elastic Email email testing tool. Furthermore, you should also follow the instructions on how to set up SPF authentication for Elastic Email.

Get Specialist Deliverability and DMARC Consulting for Elastic Email