Skip to content
DMARC Pulse

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 p tag. A missing tag or a typo such as p=quarantin. MXToolbox does not document whether this shows the warning or its DMARC Syntax Invalid result. RFC 9989 has receivers act as if the record said p=none when rua holds a valid address. Without one, they apply no DMARC processing. Gmail's 550 5.7.40 covers records that do not specify a policy, so if you send bulk mail, set p=none first.
  • 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.

  1. 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.

    TXT
    v=DMARC1; p=none; rua=mailto:dmarc@example.com
  2. 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.

  3. 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.

  4. Change p to quarantine in that same record. Caution: receivers can now send failing mail to spam, including mail from a sender you missed. With no sp tag, existing subdomains without their own DMARC record follow the new p, so check them in your reports first. sp=none keeps them at none.

    TXT
    v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
  5. Move to p=reject only 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 publish p=reject. Those that do should first spend at least a month at none and as long at quarantine. Your mail also needs a valid DKIM signature, because RFC 9989 forbids relying on SPF alone at p=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

  1. Repeat the nslookup query. You should see one record that starts with v=DMARC1 and contains p=quarantine or p=reject.

  2. If the old value still appears, a resolver may hold it until its TTL, the DNS cache lifetime, expires. Wait and query again.

  3. Run our DMARC checker, then repeat the MXToolbox lookup. The warning should clear once p is quarantine or reject.

  4. Keep reading your reports. If a legitimate sender starts failing, return to p=none while you fix it.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Is DMARC Quarantine/Reject policy not enabled an error I have to fix today?
Usually not. MXToolbox calls it a warning, and a Plesk support article says it can be ignored. It does not report a delivery failure. The exception is a record with no valid p tag: if you send bulk mail, set p=none now, because Gmail can block that mail with 550 5.7.40. Otherwise, plan the change if spoofing of your domain worries you, and read your DMARC reports first.
Does Gmail show the message DMARC Policy Not Enabled?
We did not find it in Google's sender guidelines, sender FAQ, SMTP error list or Postmaster Tools dashboards page. The wording comes from MXToolbox reports. Gmail bounces use SMTP codes, such as 550 5.7.26 and 550 5.7.40, with their own text.
Do Gmail, Yahoo or Microsoft require quarantine or reject?
Their published bulk-sender rules do not. Google says the policy can be set to none. Yahoo asks for at least p=none with DMARC passing. Microsoft asks for at least p=none, aligned with SPF or DKIM. A p=none record covers the policy part only, so SPF, DKIM and alignment still have to work.
Can moving to p=quarantine stop my email from arriving?
It can keep mail out of the inbox for any sender that fails DMARC. Google says those messages go to the recipient's spam folder. Read your aggregate reports first and fix legitimate senders. If one starts failing after the change, return to p=none while you fix it.
Can I use pct to move to quarantine gradually?
Not reliably. RFC 9989 removed the pct tag because percentages were usually applied inaccurately, although Google's rollout page still shows it. The RFC has no percentage rollout. Its t tag keeps only the old pct=100 and pct=0 behavior: t=n is the default, and t=y is a test mode that asks receivers to apply one policy level below the one you publish. With p=quarantine and t=y, RFC 9989 says a policy of none is applied, but t is new: a receiver that has not implemented it must ignore the unknown tag, so p=quarantine stands as published. We found no t tag in Google's DMARC documentation, so do not count on t=y to protect your mail.
Why does the warning stay after I changed the record?
Query the record directly. If you only added rua and stayed at p=none, that is expected: the warning stays until p is quarantine or reject. If you changed p and the query still shows p=none, your change is not live or a resolver is caching the old answer. If two DMARC records exist, RFC 9989 tells receivers to discard them all, so delete the extra one.

Sources consulted

RFC 1035 §3.2.1 (TTL)
checked 2026-11-08
Google: Set up DMARC
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.