{"id":16702,"date":"2020-03-29T12:22:33","date_gmt":"2020-03-29T12:22:33","guid":{"rendered":"https:\/\/easydmarc.com\/blog\/?p=16702"},"modified":"2025-07-30T14:15:29","modified_gmt":"2025-07-30T14:15:29","slug":"dmarc-policy-overrides","status":"publish","type":"post","link":"https:\/\/easydmarc.com\/blog\/dmarc-policy-overrides\/","title":{"rendered":"DMARC Policy Overrides"},"content":{"rendered":"

When analyzing DMARC Aggregate reports<\/a>, you may come across Policy Overrides, listed on the “Forwarded” tab. In most cases, the recipient server will apply the DMARC-Record-Specified Policy on your domain. But there may be exceptions, where DMARC Policy Override occurs.
\nSo, let\u2019s break this into 2 different cases, where Policy Override occurs:<\/p>\n

Case 1:<\/strong> When you have an enforced DMARC<\/a> Policy (p=quarantine or p=reject) and your outgoing email goes through a mailing list which breaks SPF and DKIM Authentication checks<\/a>
\nCase 2:<\/strong> Due to modification of the content and structure of original email, DKIM signature integrity broke on the way to the final destination<\/p>\n

In these two given cases, DMARC will Fail but the recipient server identifies it as either legitimate or sure forwarder, thus overriding applied DMARC Policy and accepting the email.<\/p>\n

\"DMARC<\/p>\n

DMARC Policy Override examples<\/h2>\n

Here are the screenshots of well-known DMARC Policy overrides that you may encounter in your EasyDMARC dashboard:<\/p>\n

1- Local_policy<\/strong><\/p>\n

\"DMARC-Local-Policy\"<\/p>\n

2- Forwarded<\/strong><\/p>\n

\"DMARC-Forwarded\"<\/p>\n

Some of the common DMARC Policy overrides are described below:<\/p>\n