Why does a source fail DMARC, and what does its sentence mean?
On every plan
Each source gets a sentence that says what happens to its mail and why. When something needs fixing, it also gets one action, such as "Turn on DKIM for your own domain in Mailchimp." Expand a source on the domain's Sources page to read both, or open the source's own page.
What the explanation shows
- The case that covers most of the source's mail, with its share, such as "180 of 200 messages", and its sentence. When the source needs attention, the case that needs a fix comes first, however little mail it covers.
- The next largest cases, each with its own count and sentence. Up to four cases show.
- What to do. A case that needs a fix ends its sentence with the action, so each action shows once, under the case it belongs to. The source's action, for its status and its guide link, is the first one its cases ask for, starting from the case with the most mail.
The source's own page adds why we think the source is what it is (see sources) and, when there is an action, a link to the guide for it.
The status beside each source
- Fine: at least 98 percent of its mail passes DMARC.
- Needs attention: less of it passes, and the source is a service we know or sends at least 1 percent of your mail.
- Unknown: less of it passes, and the source is a small one we cannot name.
The actions, and where they lead
Every action is one of these:
- set up DKIM for your domain in the service;
- turn on DKIM for your own domain in the service, in place of the service's own signature;
- turn on custom DKIM and a custom bounce domain in the service;
- say that the service cannot sign mail with your domain, when its own pages describe no setting for it;
- check the DKIM key in DNS;
- fix the SPF record;
- set up the service for your domain, or confirm nobody uses it;
- find out who sends from the source before a stricter policy.
The link goes to the section of that service's own guide when the guide covers the action. Otherwise it goes to the general guide for the action, with the service named in it. For a service that cannot sign, that is the service guide's section on signing with your own domain, or the general section on services that cannot sign. A source whose mail passes needs no action, and when its service cannot sign, its sentence ends with that fact instead.
When the provider's count and ours differ
A report row carries the mailbox provider's own DMARC result and the raw SPF and DKIM results. We work out the result again from the raw results. When the two differ, the provider's result counts, because the provider decided what happened to the mail. The sentence then ends with "We computed a different result from the mailbox provider. The provider's count is what is shown."
Forwarded and mailing-list mail
Forwarding breaks SPF, and a mailing list that changes a message breaks its DKIM signature. When the mailbox provider marks a failure as forwarded mail or as a mailing list, the sentence says so and ends with "Nothing to fix on your side." For forwarded mail, it also says whether the provider delivered the mail, sent it to the spam folder or refused it. The mail left your own systems correctly.
Small and large unknown sources
A source we cannot name, with no SPF or DKIM that passes, gets one of two sentences:
- When it sends at least 1 percent of your mail or at least 50 messages, the sentence says that either a service you use is not set up for your domain, or someone is sending as you at scale. Find out which before a stricter policy.
- When it is smaller, the sentence says that if this is not a service you use, it is someone else sending as you, and a reject policy would stop it.
Old reports get new sentences
We work out the sentence each time you open the page, from the results stored with each report. When we improve a sentence, the improvement reaches every report you already have.
Every case
Here is every sentence a source can get, shown with example.com as your domain and Mailchimp as the service.
| What we tell you about a source |
|---|
| SPF and DKIM both pass and both align with example.com. Nothing to do. |
| DKIM passes with selector k1 and aligns with example.com. SPF passes for mail1.mcsv.net, which is Mailchimp's bounce domain, so it does not count for DMARC. This is normal for Mailchimp. Nothing to do. |
| DKIM passes and aligns with example.com. SPF passes for mail1.mcsv.net, a different domain, so it does not count for DMARC. Mail passes through DKIM alone. |
| DKIM passes and aligns with example.com. SPF fails, which happens when mail is forwarded or when Mailchimp is missing from your SPF record. DKIM alone passes DMARC. Gmail and Outlook.com also ask bulk senders for SPF to pass, so fix it if this is your own mail. |
| SPF passes and aligns with example.com. There is no DKIM signature. This mail passes DMARC today and fails when someone forwards it, because forwarding breaks SPF. |
| SPF passes and aligns with example.com. DKIM is signed by mcsv.net, which belongs to Mailchimp, not to you, so it does not count. This mail passes DMARC today and fails when someone forwards it. |
| SPF passes and aligns with example.com. DKIM is signed with example.com (selector k1) but the signature does not verify, so this mail passes on SPF alone. The key at k1._domainkey.example.com may not match what Mailchimp signs with. |
| The mailbox provider counted this mail as passing DMARC, though we could not tell why from the details it sent. |
| The mailbox provider recognised this as forwarded mail and delivered it although it failed DMARC. Forwarding breaks SPF by design, and this forwarder did not keep the DKIM signature intact. Nothing to fix on your side. |
| A mailing list re-sent this mail with changes, which broke the signatures. The mailbox provider delivered it anyway. Nothing to fix on your side. |
| This mail failed DMARC, and the mailbox provider applied its own rule (local_policy) instead of your policy. |
| The mailbox provider could not evaluate example.com's SPF record (permerror). A broken SPF record fails every message that relies on it. |
| The mailbox provider could not look up example.com's SPF record at that moment, so SPF did not count for this mail. A lookup that fails now and then is not a fault in your record. Nothing to fix on your side. |
| Mailchimp sends this mail under its own domains: DKIM by mcsv.net and SPF for mail1.mcsv.net. Neither aligns with example.com, so every message fails DMARC. |
| DKIM is signed by mcsv.net, which belongs to Mailchimp, not to you, and SPF fails. |
| DKIM is signed by mcsv.net, not by example.com, and SPF fails. |
| SPF passes for mail1.mcsv.net, not for example.com, and there is no DKIM signature for example.com. This mail goes through Mailchimp without example.com set up there. |
| DKIM is signed with example.com (selector k1) but the signature does not verify, and SPF does not align. A missing or rotated key looks exactly like this. |
| No authentication from Mailchimp: no DKIM signature for example.com, and SPF fails. Mailchimp is not set up for example.com. If nobody at your organization uses Mailchimp, someone else is sending as you. |
| No authentication at all from Mailchimp. If this is not a service you use, it is someone else sending as you, and a reject policy would stop it. |
| No authentication at all from Mailchimp, and it is 12% of your mail. Either a service you use is not set up for example.com, or someone is sending as you at scale. |
Published 27 October 2026 · Checked 27 October 2026