DMARC: potential problem found

We found a DMARC record with a policy of "quarantine" or "reject". This might cause severe deliverability issues.

What is DMARC

In a nutshell, DMARC allows a domain owner and sender of email messages to ask mailbox providers not to deliver unauthorized messages that appear to have been sent from the same domain.

This helps in the prevention of phishing schemes and spoofing attacks.

Technically speaking, DMARC – which stands for Domain-based Message Authentication, Reporting & Conformance – is a system that builds on the DKIM and SPF authentication protocols to help receiving servers (e.g. Gmail, Yahoo!, Hotmail, etc.) know what to do when a message cannot be authenticated. It does so by establishing a "policy", which will instruct email receivers to monitor, quarantine, or reject the messages.

Why it matters

Financial institutions and other companies that are the subject of phishing and spoofing attacks can better protect themselves by implementing a DMARC policy.

This is typically not something that you need to worry about unless you are concerned about your company being the victim of phishing and spoofing attacks.

Using DMARC

Incorrectly configuring a DMARC record can have a substantial, negative effect on deliverability.

Please open a support ticket and ask to be put in touch with our Deliverability Team to discuss your current implementation of DMARC.