DKIM, SPF and Sender ID

It is very common for spam emails to claim to be from one place, when in fact sent from completely different mail servers. The same behaviour is what happens when your sender email address sends mail through our mail servers. It can be perceived as a negative thing by a spam filter when it tries to assess your email.
The spam filter looks through many other parameters as well before it classifies a mail as spam or not.

To reduce the risk of being perceived negatively by a spam filter, it is possible to add a DKIM setting on the domain used by the sender address (the domain is what comes after the @ sign). It is a confirmation on the domain that the mail that goes through our mail servers are not “fishy” in any way.

So if you use an @example.com address as the sender, you can add this setting on your domain example.com

DKIM – DomainKeys Identified Mail

getanewsletter._domainkey.example.com CNAME key1._domainkey.gansend.com

You add the setting on your domains name servers. It is a subdomain.
Do you have a .se or .nu domain, you can check out which name servers it got here – www.iis.se
Do you have anything else in the end, you can check it out here – www.who.is
Those who help you with your domain can most likely help you to add this setting.

When it is done come back to us at support@getanewsletter.com so we can fix the last thing that is needed from our side as well, so the verification can go through all the way.

SPF-Record (Sender Policy Framework)

SPF- record (Sender Policy Framework) is a simple email-validation anti-spam technique designed to reduce the risk of being marked as spam by the receiving mail exchanger (e-mail client). The mail exchanger checks that incoming mail from a domain (the sender) comes from a host authorized by that domain’s administrators (Get a Newsletter).

The list of authorized sending hosts for a domain is published in the Domain Name System (DNS) records for that domain in the form of a specially formatted TXT record. By adding an SPF record you have the ability to specify which servers are allowed to send email from your domain, eg, Get a Newsletter. This makes it harder for someone to prevent spammers from using your domain as a sender of spam

Implement an SPF-record

In order to configure an SPF record you need your DNS settings to specify by using an SPF record that to your own domain will send newsletters from Get a Newsletter. This way, the receiving mail server can easily check, verify your domain and forwarding your email to the receivers inbox folder- instead of the rubbish bin. Bare in mind that your newsletters are sent from our servers.

In order to implement a SPF record, include the following:

include:spf.gansend.com

Example of what a SPF-record can look like:

v=spf1 mx a include:spf.gansend.com ~all

Sender ID

Sender ID is based on and very similar to the SPF record , and are also made in the DNS settings , but looking at some other things so they complement each other.

”spf2.0/mfrom,pra a mx include:spf.gansend.com ~all”

 

Information for the inquisitive

Good to know about DKIM
https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail

Good to know about SPF records
https://en.wikipedia.org/wiki/Sender_Policy_Framework

Website were you may create SPF-Records
Don’t have a SPF record? You can easily create one by using the information from any of the following websites:

http://www.openspf.org/
http://randsco.com/index.php/2007/02/07/writing_an_spf_record
http://www.openspf.org/FAQ/Common_mistakes

Test your SPF-record
See if your SPF-record is valid by using any on these websites:

http://www.kitterman.com/spf/validate.html
http://old.openspf.org/why.html

Good to know about Sender ID
https://en.wikipedia.org/wiki/Sender_ID
https://sendgrid.com/blog/sender-id-email-authentication-what-you-need-to-know/

What is a DMARC record?
https://dmarc.org/overview/

 

Related article:

  • How to avoid spam filters
    This article goes through some points to consider and what tests you can do, to see if things gets better.