Getting stuck on p=none
With p=none you receive reports, but nobody blocks anything. Many organisations stay there for years. See none as the first step: map your senders, move to quarantine and then to reject.
Domain check / DMARC
<DMARC>DMARC tells recipients how to handle your domain. Is the sender genuine? Then your email arrives properly. Does something not check out? Then misuse is stopped. That way you stay in control of who can send email on behalf of your domain, and you improve the delivery of your own messages.
DMARC is the only one of the three that protects the sender address the recipient actually sees. It checks whether SPF or DKIM passes and whether that domain matches the address in the From field. If not, your policy decides what the recipient does: nothing, the spam folder or reject.
On top of that, recipients send you reports on all email sent on behalf of your domain, including phishing. That shows you who sends on your behalf, and what goes wrong.
Google, Yahoo and Microsoft require DMARC from organisations that send a lot of email. For Dutch government bodies, DMARC is on the list of mandatory standards. And customers and insurers ask about it more and more.
_dmarc.yourdomain.com (TXT)
v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r
| Part | What it means |
|---|---|
p=reject | The policy: none (report only), quarantine (spam folder) or reject. |
rua=mailto:… | Where the daily reports go. Usually an address of a DMARC service. |
adkim=r / aspf=r | How strictly the domain must match. r (relaxed) allows subdomains and is usually the right choice. |
sp= | Optional: a separate policy for subdomains. Without sp, the rules of p also apply to subdomains. |
pct= | Optional: the percentage of email the policy applies to. Leave it out for 100%. |
With p=none you receive reports, but nobody blocks anything. Many organisations stay there for years. See none as the first step: map your senders, move to quarantine and then to reject.
If you switch on reject before all genuine senders are set up correctly, your own email gets rejected. Think of the accounting software that sends invoices, the web shop, the CRM or the scanner that scans to email. Only move to reject when the reports are clean.
DMARC reports are XML files, often dozens a day. Without a tool, nobody looks at them, and you have no idea what is happening. Have them processed by a DMARC service that turns them into readable overviews.
Attackers like to use subdomains or domains you do not actively use. Make sure sp is not set to none, and give domains that do not send email a DMARC record with p=reject as well.
Brandaris works with DMARC Advisor, the Dutch DMARC specialist that has been around since 2013. With DMARC Advisor's DMARC Manager we make the reports readable: which services send on your behalf, what goes well and what does not. That way we take you from none to reject in steps, without genuine email getting caught. After that, we keep an eye on the reports.
With none, recipients only report. With quarantine, suspicious email goes to the spam folder. With reject, that email is refused. Only quarantine and reject really protect you against misuse.
For Dutch government bodies, DMARC is on the list of mandatory standards. Google, Yahoo and Microsoft require it from organisations that send a lot of email. And customers and insurers ask about it more and more.
That depends on the number of services sending on your behalf. We only move to reject when all genuine senders are set up correctly. For most organisations that takes a few weeks to a few months.
Receiving mail servers send daily overviews of all email sent on behalf of your domain, including fake email. Those reports are technical. A DMARC service makes them readable.
Yes. Those are exactly the ones that get misused, because nobody watches them. Put v=spf1 -all and a DMARC record with p=reject on them.