How Do I Fix “DMARC Policy Is Not Enabled”?

To stop coming across the prompt, “DMARC policy not enabled”, you will need to configure DMARC for your domain. Configuring DMARC on your domain protects you against spoofing and phishing. These prompts usually appear while doing a reverse DNS lookup. This article will tell you how to configure your DMARC properly and stop the prompts.

Configuring DMARC
DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication standard or protocol that determines whether an email is authentic or not. It relies on SPF and DKIM, two other protocols, to decide the authentication status of an email. It provides visibility of the sources sending emails from an organization’s domain, ensures better email deliverability, and, most importantly, provides security against domain spoofing, phishing, and impersonation attacks.

For detailed information, read more on What is DMARC?

To implement DMARC for your domain, follow these steps:

• Log into your DNS management console and go to the records section.
• Use EmailAuth’s DMARC record generator to generate a DMARC record and publish it in your DNS.
• Wait for the changes to take effect and check your record using EmailAuth’s free DMARC record lookup tool.

Fix “DMARC Quarantine/Reject Policy Not Enabled”

If a warning pops up saying “DMARC Quarantine/Reject policy not enabled”, it means that your domain is configured with a ‘none’ DMARC policy. A ‘none’ policy offers zero security and is used only for the purpose of monitoring; hence, it is necessary to configure either ‘quarantine’ or ‘reject’ policy.

To set up a ‘reject’ or ‘quarantine’ policy, modify the record as follows:

v=DMARC1; p=reject; rua=mailto:example@domain.com; ruf=mailto:example@domain.com;

v=DMARC1; p=quarantine; rua=mailto:example@domain.com; ruf=mailto:example@domain.com;

Now that you have fixed the prompt, DMARC is successfully configured and your domain is protected against malicious spoofing and phishing attacks.