DMARC Quarantine vs. DMARC Reject: Which Should You Implement?

Editor’s Note: This blog post was originally found on the Agari Email Security blog.

By Fareed Bukhari

You did it! You implemented DMARC and authenticated your email domains. This is no easy feat in itself and now, after DNS requests, third-party conference calls, and writing internal policies, you are ready… It’s time for a stricter DMARC policy.

If your DMARC policy has been set to p=none for months, you’ve likely had the chance to review who is sending email under your brand name and determine which of those are legitimate — and which are not. This is an important step in any DMARC implementation and is necessary in order to make sure that legitimate senders are not blocked from delivering email once the policy becomes more strict. Without spending some time reviewing those senders, a stricter DMARC policy could result in legitimate emails from third-party senders like Marketo, Salesforce, and Mailchimp from being delivered to your customers, partners, and employees.

Unfortunately, while you’re living in the world of p=none, spammers and cybercriminals can still take advantage of your domain. Only by implementing a stricter policy will you be able to block them at the door and let the world know that you truly care about your consumers and your brand.

The question thus becomes, which policy will you choose? Do you go immediately to p=reject, or do you dabble with p=quarantine? Which is truly the better option for your organization?

Before making your decision whether to implement DMARC Reject or DMARC Quarantine, you should understand what happens when you implement either policy.

Implementing a p=quarantine DMARC Policy

  • Quarantine: If the email receiver has a quarantine mailbox, this is where the message will be delivered. It will then be up to the administrator of the mailbox to decide if the email gets delivered or thrown away.
  • Deliver to spam: If the email receiver hosts the recipient’s mailbox, then the receiver may have the option to deliver non-compliant email into the recipient’s spam folder. The receiver would then have the option to determine if he or she would like to move it to the inbox.
  • Aggressive anti-spam filtering: Most receivers will see quarantined messages as something that is spam-like and could add additional scoring to the message itself. This additional step would allow the receiver to block the message due to its high spam scoring.

Some think quarantine is a great testing option, as it allows companies to start flexing their DMARC muscles slowly until they feel 100% confident that the right emails are passing and the wrong emails are failing. However, if DMARC is still not completely configured and you have legitimate email being quarantined or marked as spam, receivers will begin to associate the domain with the junk emails — ultimately hurting your brand. In this respect, a quarantine policy should be something to take just as seriously as a reject policy.

Implementing a p=reject DMARC Policy

The one downfall to this is if legitimate emails are failing authentication and the email gets rejected, the receiver will never know they were receiving the intended email. For those organizations not actively using a reporting system to monitor authentication, it could take months to find out that legitimate email is not being delivered, potentially hurting marketing programs or other opportunities to engage with prospects, customers, and partners.

So Which Should You Choose?

Learn more about DMARC with our Getting Started with DMARC Guide or create your record with our free DMARC tool.

Agari is the Trusted Email Identity Company™, protecting companies and people from phishing and socially-engineered email attacks.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store