<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dora on Daily DMARC News</title><link>https://news.excello.email/tags/dora/</link><description>Recent content in Dora on Daily DMARC News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 20 May 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://news.excello.email/tags/dora/index.xml" rel="self" type="application/rss+xml"/><item><title>DMARC Is Now the Law: What PCI DSS v4.0, NIS2, and DORA Mean for Your Email Program</title><link>https://news.excello.email/posts/2026-05-20-dmarc-pci-dss-nis2-dora-mandate/</link><pubDate>Wed, 20 May 2026 08:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-05-20-dmarc-pci-dss-nis2-dora-mandate/</guid><description>&lt;p&gt;For the better part of a decade, the case for DMARC rested on a single pillar: it was the right thing to do. Security teams pointed to phishing statistics. Email deliverability consultants warned about reputation damage. Vendors built dashboards to make the path from &lt;code&gt;p=none&lt;/code&gt; to &lt;code&gt;p=reject&lt;/code&gt; feel manageable.&lt;/p&gt;
&lt;p&gt;None of that moved the needle fast enough.&lt;/p&gt;
&lt;p&gt;What is moving the needle in 2026 is something organizations respond to far more reliably than best-practice guidance: the threat of fines. DMARC has crossed from recommendation into regulation, and the frameworks now requiring it carry real financial consequences.&lt;/p&gt;</description></item></channel></rss>