Authenticating GetResponse Emails with DKIM
Why are my GetResponse emails going to Spam?
If you have a problem with GetResponse 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 GetResponse emails being blocked is due to the GetResponse emails failing DMARC, which in the case of GetResponse, is usually due to a misconfiguration of DKIM.
How to stop GetResponse emails going to Junk.
The first step to preventing GetResponse 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 GetResponse emails from going to spam, or at least rule out authentication as the issue.
How to remove 'via getresponse.com' or 'on behalf of getresponse.com'
Another example of where a GetResponse DKIM misconfiguration is to blame, is if your recipients report seeing the message as 'via getresponse.com' or 'on behalf of getresponse.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 GetResponse by logging in to your GetResponse account to check to see if you have followed the following article to configure your GetResponse dkim setup to authenticate your domain.
How to stop GetResponse Failing DMARC
To ensure that your GetResponse 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 GetResponse DKIM keys. However, in order for GetResponse email to pass authentication for your own domain, it is necessary to use your own DKIM keys as per GetResponse's own guide. If you wish to verify the above, paste the message headers for a failed GetResponse message into our GetResponse email testing tool