Authenticating SocketLabs Emails with DKIM

Why are my SocketLabs emails going to Spam?

If you have a problem with SocketLabs 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 SocketLabs emails being blocked is due to the SocketLabs emails failing DMARC, which in the case of SocketLabs, is usually due to a misconfiguration of DKIM.

How to stop SocketLabs emails going to Junk.

The first step to preventing SocketLabs 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 SocketLabs emails from going to spam, or at least rule out authentication as the issue.

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

Another example of where a SocketLabs DKIM misconfiguration is to blame, is if your recipients report seeing the message as ‘via socketlabs.com’ or ‘on behalf of socketlabs.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 SocketLabs by logging in to your SocketLabs account to check to see if you have followed the following article to configure your SocketLabs dkim setup to authenticate your domain.

How to stop SocketLabs Failing DMARC

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

Get Specialist Deliverability and DMARC Consulting for SocketLabs