<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
  <title>Email Watch — Updates</title>
  <link>https://emailwatch.co/</link>
  <description>AI-powered DMARC monitoring for small businesses.</description>
  <language>en-us</language>
  <item>
    <title>What&apos;s new: September 27, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-09-27/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-09-27/</guid>
    <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
    <description>Setup and support got easier this week: DNS quote guidance, a public company page for sales and support, guides for SPF/DKIM/DMARC fixes, and a clearer staff work queue when you need help.</description>
  </item>
  <item>
    <title>DMARC alignment explained: why SPF/DKIM can pass and DMARC still fail</title>
    <link>https://emailwatch.co/guides/dmarc-alignment-explained/</link>
    <guid isPermaLink="true">https://emailwatch.co/guides/dmarc-alignment-explained/</guid>
    <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
    <description>DMARC only counts SPF or DKIM when the authenticated domain matches the From address people see. Here is how alignment works and how to fix a pass that still fails DMARC.</description>
  </item>
  <item>
    <title>How to read DMARC aggregate (rua) reports</title>
    <link>https://emailwatch.co/guides/how-to-read-dmarc-reports/</link>
    <guid isPermaLink="true">https://emailwatch.co/guides/how-to-read-dmarc-reports/</guid>
    <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
    <description>DMARC rua reports are daily XML dumps of who sent as your domain and whether SPF/DKIM aligned. Here is what to look at first, and what to ignore.</description>
  </item>
  <item>
    <title>SPF vs DKIM vs DMARC: what each one actually checks</title>
    <link>https://emailwatch.co/guides/spf-vs-dkim-vs-dmarc/</link>
    <guid isPermaLink="true">https://emailwatch.co/guides/spf-vs-dkim-vs-dmarc/</guid>
    <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
    <description>SPF checks the sending IP, DKIM checks the signature, DMARC ties both to the From address you see and decides what happens on failure. Here is how they fit together.</description>
  </item>
  <item>
    <title>What&apos;s new: September 20, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-09-20/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-09-20/</guid>
    <pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate>
    <description>New accounts and checkout are open again, and paused onboarding sequences no longer dump a backlog of late emails when they resume.</description>
  </item>
  <item>
    <title>What&apos;s new: August 30, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-08-30/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-08-30/</guid>
    <pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate>
    <description>Signup errors got clearer, and new guides walk through the SPF, DKIM, and DMARC fixes most teams need.</description>
  </item>
  <item>
    <title>Fix Gmail error 550 5.7.26: message does not pass authentication checks</title>
    <link>https://emailwatch.co/guides/gmail-550-5-7-26-spf-dkim/</link>
    <guid isPermaLink="true">https://emailwatch.co/guides/gmail-550-5-7-26-spf-dkim/</guid>
    <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
    <description>Gmail bounces mail with 550 5.7.26 when SPF and DKIM both fail DMARC alignment. Here&apos;s exactly what that means and the record fix that clears it.</description>
  </item>
  <item>
    <title>SPF permerror: too many DNS lookups, and how to fix it</title>
    <link>https://emailwatch.co/guides/spf-permerror-too-many-dns-lookups/</link>
    <guid isPermaLink="true">https://emailwatch.co/guides/spf-permerror-too-many-dns-lookups/</guid>
    <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
    <description>SPF caps you at 10 DNS lookups. Over that limit, receivers treat your entire SPF record as broken. Here&apos;s how to count your lookups and cut them back under 10.</description>
  </item>
  <item>
    <title>What&apos;s new: August 18, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-08-18/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-08-18/</guid>
    <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
    <description>A few customer-visible fixes landed this week, starting with a health badge that could read Healthy when it should not have.</description>
  </item>
  <item>
    <title>What&apos;s new: August 16, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-08-16/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-08-16/</guid>
    <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
    <description>Deleting a domain now requires typing its name first, so report history is harder to lose to a stray click.</description>
  </item>
  <item>
    <title>What&apos;s new: August 9, 2026</title>
    <link>https://emailwatch.co/newsletter/2026-08-09/</link>
    <guid isPermaLink="true">https://emailwatch.co/newsletter/2026-08-09/</guid>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <description>Domain health scoring got more accurate, onboarding mail started sending real bodies, and free-tool CTAs point into the 7-day trial.</description>
  </item>
</channel>
</rss>
