Email errors
DMARC Quarantine/Reject Policy Not Enabled: How to Fix It
DMARC Quarantine/Reject policy not enabled means your record does not ask receivers to quarantine or reject failing mail. See how to enforce it safely.
What this means
DMARC Quarantine/Reject policy not enabled is a warning from the MXToolbox health check: your DMARC record does not ask receiving servers to quarantine or reject mail that fails DMARC. DMARC is a DNS record that tells receivers how to treat mail failing authentication for your From domain, and its p tag holds the policy.
MXToolbox's help page is titled DMARC Policy Not Enabled, and its sample result reads No DMARC Protection.
The warning alone does not report a delivery failure. RFC 9989, the current DMARC standard, says p=none must not change how receivers handle your mail. The drawback is spoofing: your record does not ask receivers to quarantine or reject a forged message.
A Gmail bounce such as 550 5.7.40 or 550 5.7.26 is a separate problem, because it reports blocked mail.
Why it happens
Read the published record first, with your own domain in place of example.com:
nslookup -type=TXT _dmarc.example.com 1.1.1.1
Then match the result:
p=none. RFC 9989 says domain owners usually start there, and Plesk publishes it by default.- No valid
ptag. A missing tag or a typo such asp=quarantin. MXToolbox does not document whether this shows the warning or itsDMARC Syntax Invalidresult. RFC 9989 has receivers act as if the record saidp=nonewhenruaholds a valid address. Without one, they apply no DMARC processing. Gmail's550 5.7.40covers records that do not specify a policy, so if you send bulk mail, setp=nonefirst. - No record at all. MXToolbox reports that as
No DMARC Record found. Start with the no DMARC record found guide.
How to fix it
How to enable the DMARC policy
Keep one TXT record at _dmarc.example.com, starting with v=DMARC1, and raise the policy in stages (none, quarantine and reject). MXToolbox advises against setting Quarantine or Reject until you have evaluated your DMARC reports.
-
Add a reporting address if the record has none. Edit the existing record and keep its other tags: RFC 9989 tells receivers to discard all records when several exist. Without the rua tag, receivers must not send aggregate reports.
TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
-
Use the reports to list every service that sends as your domain. Google suggests at least one week at
p=none. RFC 9989 warns the review can take many months. -
Fix every legitimate sender that fails. RFC 9989 requires SPF or DKIM aligned with your From domain before you enforce. Caution: edit your one SPF record to add a sender. A second record makes SPF return
permerror. -
Change
ptoquarantinein that same record. Caution: receivers can now send failing mail to spam, including mail from a sender you missed. With nosptag, existing subdomains without their own DMARC record follow the newp, so check them in your reports first.sp=nonekeeps them atnone.TXTv=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
-
Move to
p=rejectonly after your reports stay clean. Caution: Google warns that rejected messages are never delivered. RFC 9989 says domains whose users may post to mailing lists should not publishp=reject. Those that do should first spend at least a month atnoneand as long atquarantine. Your mail also needs a valid DKIM signature, because RFC 9989 forbids relying on SPF alone atp=reject.
If your domain is on Plesk
Caution: before Obsidian 18.0.79, a Plesk bug rejected locally sent mail or moved it to spam when the recipient domain used quarantine or reject. Update Plesk first. Then, on Plesk for Linux, make each edit above at Domains > example.com > DNS Settings: click the _dmarc.example.com record, edit it, apply the changes and click Update.
Confirm the fix
-
Repeat the
nslookupquery. You should see one record that starts withv=DMARC1and containsp=quarantineorp=reject. -
If the old value still appears, a resolver may hold it until its TTL, the DNS cache lifetime, expires. Wait and query again.
-
Run our DMARC checker, then repeat the MXToolbox lookup. The warning should clear once
pisquarantineorreject. -
Keep reading your reports. If a legitimate sender starts failing, return to
p=nonewhile you fix it.