<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Email-Deliverability on Daily DMARC News</title><link>https://news.excello.email/tags/email-deliverability/</link><description>Recent content in Email-Deliverability on Daily DMARC News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 23 Jun 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://news.excello.email/tags/email-deliverability/index.xml" rel="self" type="application/rss+xml"/><item><title>You Have a DMARC Record. Without Aggregate Reports, You Cannot See Who Is Spoofing You.</title><link>https://news.excello.email/posts/2026-06-23-dmarc-rua-reporting-blind-spot/</link><pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-06-23-dmarc-rua-reporting-blind-spot/</guid><description>&lt;p&gt;The EasyDMARC 2026 DMARC Adoption Report, drawn from an analysis of the top 1.8 million global domains, contains a finding that deserves more attention than it has received: more than 70 percent of DMARC-enabled domains have no aggregate reporting configured.&lt;/p&gt;
&lt;p&gt;These organizations published a DMARC record. They are counted in the 52.1 percent adoption figure. But they added no &lt;code&gt;rua=&lt;/code&gt; tag to receive aggregate reports, which means they have no way to see who is sending email that claims to come from their domain.&lt;/p&gt;</description></item><item><title>All Three Inbox Giants Now Enforce One-Click Unsubscribe -- and the Deliverability Penalty for Getting It Wrong Is a 3x to 7x Inbox Hit</title><link>https://news.excello.email/posts/2026-06-21-one-click-unsubscribe-rfc-8058-microsoft-enforcement-deliverability-gap/</link><pubDate>Sun, 21 Jun 2026 08:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-06-21-one-click-unsubscribe-rfc-8058-microsoft-enforcement-deliverability-gap/</guid><description>&lt;p&gt;In February 2024, Google and Yahoo told bulk senders that one-click unsubscribe was no longer optional. Most senders treated it as a Google-and-Yahoo problem and updated their templates accordingly &amp;ndash; or believed they already had it covered because their emails contained an unsubscribe link somewhere in the footer.&lt;/p&gt;
&lt;p&gt;In May 2026, Microsoft completed its own enforcement rollout. The requirement is now active across all three dominant inbox providers. Google, Yahoo, and Microsoft collectively handle the vast majority of personal and business email inboxes in the world. There is no major provider left to wait for.&lt;/p&gt;</description></item><item><title>Google Postmaster Tools v2 Added a Deliverability Analysis Checklist -- And the 0.3% Spam Rate Is Now a Kill Switch</title><link>https://news.excello.email/posts/2026-06-19-google-postmaster-tools-v2-deliverability-analysis-june-2026/</link><pubDate>Fri, 19 Jun 2026 08:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-06-19-google-postmaster-tools-v2-deliverability-analysis-june-2026/</guid><description>&lt;p&gt;For years, Google Postmaster Tools gave senders a reputation label &amp;ndash; High, Medium, Low, or Bad &amp;ndash; and left them to figure out what was causing the problem. The labels were opaque by design. You could watch your reputation slide from High to Medium and have no direct signal as to whether the culprit was your SPF configuration, your DKIM signing, your list quality, or something else entirely.&lt;/p&gt;
&lt;p&gt;That model is gone. Google retired Postmaster Tools v1 in 2026, and in early June the company added a new Deliverability Analysis section to the Compliance Status page in v2. The new section replaces the reputation label system with an explicit compliance checklist. You can now see exactly which authentication requirement is failing, exactly where your spam rate sits relative to the thresholds that trigger enforcement, and exactly what is sending your mail to the spam folder or to outright rejection.&lt;/p&gt;</description></item><item><title>The SPF Time Bomb in Your SaaS Stack: How the 10-Lookup Limit Silently Kills Email Deliverability</title><link>https://news.excello.email/posts/2026-05-30-spf-lookup-limit-saas-sprawl-email-deliverability/</link><pubDate>Sat, 30 May 2026 09:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-05-30-spf-lookup-limit-saas-sprawl-email-deliverability/</guid><description>&lt;p&gt;Every organization that has grown its software stack over the past few years carries a potential deliverability fault line inside a DNS record most people never look at. The SPF record, a short TXT entry that authorizes which servers are allowed to send email on behalf of your domain, was designed for a simpler era. RFC 7208, the standard that governs SPF, imposes a hard limit of 10 DNS mechanism lookups per evaluation. In 2026, with the average mid-sized organization running Microsoft 365, a CRM, a marketing platform, a transactional email service, a customer support tool, and several more SaaS applications that all send email bearing the company domain, that limit is not a theoretical edge case. It is a trap that teams walk into every time they provision a new tool.&lt;/p&gt;</description></item></channel></rss>