<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dkim on BitPage</title><link>https://bitpage.me/tags/dkim/</link><description>Recent content in Dkim on BitPage</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 07:08:22 +0000</lastBuildDate><atom:link href="https://bitpage.me/tags/dkim/index.xml" rel="self" type="application/rss+xml"/><item><title>Gmail bounced 1,429 messages in a day: three broken auth mechanisms and a silent OpenDKIM</title><link>https://bitpage.me/incidents/gmail-bounces-everything-spf-dkim-fcrdns/</link><pubDate>Thu, 06 Aug 2026 07:08:22 +0000</pubDate><guid>https://bitpage.me/incidents/gmail-bounces-everything-spf-dkim-fcrdns/</guid><description>Short answer: Three independent mechanisms were broken at once, and fixing any one of them changed nothing visible. The domain had no v=spf1 record (only a dead SenderID one), the PTR resolved forward to a different server, and OpenDKIM was signing nothing because KeyTable and SigningTable were attached as refile: while their contents were in plain two-column format. That last one cost the most time: when OpenDKIM can&amp;rsquo;t find a key it logs absolutely nothing, so the daemon reads active, the config parses, the key is readable, and mail still leaves unsigned.</description></item></channel></rss>