de en


DKIM and sender domains: DMARC

Domain settings have a considerable influence on your deliverability rates. Incoming mail servers therefore pay particular attention to these entries. They are used to check the authenticity of a newsletter and thus protect the recipient from phishing and spoofing. The SPF and DKIM records of your domain serve this purpose above all. If such a check fails, the incoming mail server decides at its own discretion how to handle the newsletter. One provider moves it straight to the spam folder, another does not deliver it at all.

Improving newsletter delivery

The DMARC policy of your domain tells the incoming mail server what should happen to a newsletter that is not authentic. In addition to valid SPF and DKIM records, your domain should therefore also have a DMARC policy. Otherwise, the delivery of your newsletters will be considerably impaired in the future, because they will be rejected automatically.

In the DKIM and sender domains menu, you can display simple examples of DMARC policies. The following variants are possible:

  • none: No action is taken if a newsletter appears suspicious
  • quarantine: Suspicious newsletters are moved to the recipient's spam folder
  • reject: Suspicious newsletters are discarded immediately, so they are not delivered to the recipient

Optional settings

DMARC was developed to protect your recipients. To make full use of this protection, you should therefore also set up more complex DMARC policies in the long term. The following settings are suitable for this:

  • adkim/aspf (DKIM alignment/SPF alignment): Strictness when checking DKIM/SPF records
  • sp (subdomain policy): Defines the behavior for subdomains
  • fo (failure reporting): Enables reports on failed DKIM and/or SPF checks
  • ruf/rua/rf/ri: Defines the format, interval and recipients of reports
  • pct (percentage): Percentage of all incoming newsletters that go through the DMARC check

Risks of DMARC policies

While none and quarantine leave the final assessment of suspicious newsletters to your recipients, reject lets you, as the sender, prevent this from the very start. In theory, the reject variant therefore protects your recipients from fake newsletters sent in your name. In practice, however, there are some cases in which legitimate newsletters also fail the DMARC check. This can happen in particular with automatically forwarded emails.

We therefore recommend starting with none or quarantine and observing the opening behavior over a longer period with the help of reports. This way you make sure that all special cases are known before you use reject.

DMARC reports

Evaluating DMARC reports helps you optimize your policies. All you need is a separate mailbox. As soon as it is specified in the corresponding policy, you should receive reports there. Once you have them, we recommend aggregating them with analysis tools (e.g. dmarcian or DMARC Advisor). These tools specialize in DMARC parameters and make potential improvements much easier to see.

Tags: