Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

DMARC fail: what p=none, quarantine and reject ask a receiver to do

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A DMARC result of fail means the receiver found a policy and the message did not pass it. RFC 7489 registers that result for the method dmarc. The meaning is: "A DMARC policy record was published for the aligned identifier, and none of the authentication mechanisms passed."

Fail is not the same as a missing record. The result none means no DMARC policy record was published for the aligned identifier, or no aligned identifier could be extracted. temperror is a temporary evaluation error. permerror is a permanent one, such as a syntactically incorrect record. Only fail means a policy was found and nothing passed.

What the receiver does with a failure is the p= tag. none asks for no specific action. quarantine asks the receiver to treat the mail as suspicious. reject asks the receiver to reject it during SMTP. A receiver can still do something else. The result tells you the evaluation. The policy tells you what the domain asked for.

What the symptom means

Section 6.6.2 is the evaluation. The receiver takes the domain from the From: header, looks up the DMARC TXT record, checks DKIM and SPF, then checks identifier alignment. If one or more authenticated identifiers align with that From: domain, the message passes. All other conditions, including authentication failures and identifier mismatches, are DMARC mechanism check failures.

Section 11.1 registers the method name dmarc, with the property from taken from the domain in that header. Receivers that follow the recommendation in section 6.7 add an Authentication-Results header when they deliver mail that failed the check. The result name in that header is the registered code. People write the fail case as dmarc=fail. The registry's word is fail, for the method dmarc.

The policy record is a TXT record at _dmarc under the domain. Section 6.1: the owner of example.com publishes it at _dmarc.example.com. The tag p is required on a policy record. The values are:

  • none: the domain owner requests no specific action be taken regarding delivery.
  • quarantine: the owner wishes mail that fails the check to be treated as suspicious. Depending on the receiver, that can mean placing it in a spam folder, scrutinising it further, or flagging it.
  • reject: the owner wishes receivers to reject mail that fails the check. Rejection should happen during the SMTP transaction.

Section 6.6.4 says a receiver should quarantine mail that is subject to quarantine, and should reject mail that is subject to reject. The pct tag defaults to 100. Mail not selected for reject because of pct should be treated as quarantine. Section 6.7 allows a receiver to accept a failure even when the domain published reject, and to reject mail that passed. A delivered message can still show fail.

Gmail's SMTP errors page has a 5.7.26 text for this case: "Unauthenticated email from domain-name is not accepted due to domain's DMARC policy." Other receivers may quarantine, or deliver and record fail.

Likely causes

Cause What you see How to confirm
SPF and DKIM both failed, or were not aligned with the From: domain dmarc result fail, and the underlying checks did not pass The Authentication-Results line, and the TXT record
The policy is p=none fail is recorded, and the mail is still delivered The p= tag. none asks for no specific action
The policy is p=quarantine The message is in a spam or quarantine folder, or is flagged Section 6.3's description of quarantine
The policy is p=reject An SMTP reject, or Gmail's 5.7.26 DMARC text The p= tag and the bounce
The record is missing or broken Result none or permerror, not fail A fail result requires a published policy

Prove the cause before changing anything

All of these are read-only.

1. Read the result you were given. A fail result means the mechanisms did not pass. A none result means there was no policy to fail. Do not publish a stricter p= to "fix" a none until mail is passing.

2. Read the published policy. RFC 7489's example is:

dig +short TXT _dmarc.example.com.

The sample answer in the RFC is v=DMARC1; p=none; rua=mailto:dmarc-feedback@example.com. Your p= value is the request receivers are being asked to honour. If the set of records is empty, section 6.6.3 says the receiver also queries the organisational domain. A fail on mail from a subdomain can come from the organisational record.

3. See which mechanism failed. Section 6.6.2 fails the message when no authenticated identifier aligns with the From: domain. SPF can pass for the envelope domain while the From: domain is different. DKIM can pass for a signing domain that is not aligned. The fail result does not say which of those it was. The rest of the Authentication-Results header, or the receiver's bounce, does.

Fix

The lasting fix is that SPF or DKIM passes and the passing domain aligns with the From: domain, as section 6.6.2 describes. Publishing or changing SPF and DKIM records has its own save-first step, warning and undo in the Gmail 550 5.7.26 guide, so the steps are not repeated here. Lowering p= changes what the domain asks receivers to do. It does not make the message authentic.

The only change made here is the p= tag. Save the current record first. This command writes its own file. An empty file means no DMARC record was published before:

dig +short TXT _dmarc.<domain-from-the-From-header> > dmarc-before.txt

Risk: the next step changes the p= tag of the domain's DMARC record. Changing p=none to p=reject asks every receiver that honours DMARC to reject mail that fails, and mail that is not yet aligned will start bouncing. Changing p=reject to p=none stops that request. It does not repair SPF or DKIM. Section 6.7 says final disposition of a message is always a matter of local policy: a receiver may reject or quarantine mail that passes, and may accept mail that fails even when the policy is reject.

Keep p=none until a message from each sending path shows a pass. The Gmail sender guidelines allow a DMARC enforcement policy of none for bulk senders while authentication is in place. When you do change the tag, change it in the same TXT record, at _dmarc under the domain, in one edit. Section 6.6.3 says that if multiple records remain, or no record remains, policy discovery stops and DMARC is not applied. Two TXT records at _dmarc are not a stricter policy. They are no policy.

To undo it: publish the TXT value that dmarc-before.txt holds again. If the file is empty, delete only the DMARC record you published.

Example (illustrative): Authentication-Results shows a DMARC fail for example.com, and dig +short TXT _dmarc.example.com. returns v=DMARC1; p=quarantine. The SPF result is pass for mail.example.net, and the From: domain is example.com. Those domains are not aligned, so the check fails and the receiver quarantines. The administrator signs the message with DKIM for example.com, or sends with an envelope domain that aligns, and leaves p=quarantine until a test shows pass. They do not move to p=reject on the same day.

Confirm the fix

  1. The _dmarc query returns one record, and p= is the value you intended.
  2. A new message from the same system shows a DMARC result of pass, not fail.
  3. If the policy is quarantine or reject, a message that still fails is treated that way. A pass should not be quarantined for DMARC. A receiver can still filter it for other reasons. Section 6.7 says a pass does not mean the mail is good.

What to watch afterwards

  • Add a new sending service to SPF and DKIM before you rely on p=reject.
  • Subdomains use the organisational domain's policy when they have no record of their own. The p tag applies to the domain queried and to its subdomains, unless the record describes a subdomain policy with the sp tag (section 6.3).
  • pct below 100 means only part of the failing mail gets the published action. The rest of a reject policy is treated as quarantine.
  • Aggregate reports, when you publish rua, are how you see failures that receivers did not bounce to you.

Risks and limits

  • RFC 7489 defines the result names and the policy requests. It does not require every receiver to enforce them. Gmail's 5.7.26 text is one enforcement. Another receiver may deliver the same fail.
  • A fail result is cleared by a passing, aligned SPF or DKIM mechanism. Changing p= does not create those records.
  • p=none still produces fail when nothing passes. Monitoring and enforcement are different tags.

Sources