"DMARC Policy Not Enabled"

How to Fix “DMARC Quarantine/Reject Policy Not Enabled”

When you get a warning of “DMARC Quarantine/Reject policy not enabled” or sometimes just “DMARC policy not enabled” or “ No DMARC protection” that simply indicates that your domain is configured with a DMARC policy of none that allows monitoring only.

If you are just starting out on your email authentication journey, and you want to monitor your domains and email flow to ensure smooth email delivery, then we recommend you start off with a DMARC policy of none. However, a none policy offers zero protection against spoofing, and hence you will come across the frequent prompt: “DMARC policy not enabled”, where you are reminded that your domain isn’t adequately protected against abuse and impersonation.

In order to fix this, all you need to do is modify the policy mechanism (p) in your DMARC record from p=none to p=reject/quarantine, thereby shifting to DMARC enforcement. If your DMARC record was previously:

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected];

Your optimized DMARC record will be:

v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected];

Or, v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected];

Fixing [Error] “DMARC Policy Not Enabled Cloudflare”

If you are using Cloudflare as your DNS hosting provider, you may come across this error. To get rid of this error in Cloudflare,

• Log in to your Cloudflare account to view your DNS management console
• Select your domain name
• From the left-hand side menu bar, select “DNS”
• Under the DNS management section for your domain, click on “Add Records”

NOTE: while creating your DMARC record, make sure you choose an appropriate policy mode. The p= field shouldn’t be blank for your record. 

• In the add records section, set Type as “TXT”, TTL “Auto”, Name “_dmarc” and in the value field paste the value generated by the tool.
• Save changes