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.
Quarantine lets the participating email receivers know that you would like them to treat email that fails the DMARC authentication check with extra caution. The email will still be accepted by the receiver, but the receiver will decide how they want to implement the quarantine policy.
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.
Setting a DMARC policy to p=reject will allow you to ensure that all malicious email is stopped. As an added bonus, the recipient of the intended malicious email will never become aware of the email in the first place, as it will never get sent to a spam or quarantine folder. Since it is completely blocked, emails are never delivered and end-users cannot be tricked into clicking on a malicious link or opening a dangerous attachment.
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.
At the end of the day, which policy you choose is ultimately the decision of your organization as you decide which policy best suits your needs. Here at Agari, we recommend that all customers implement a p=reject policy to ensure complete protection for the recipients of your emails. That said, you have the opportunity to decide which policy best suits your needs—either is a much more secure option than p=none or no DMARC policy at all.