July 31, 2026
BIMI puts your logo in the inbox — but only after you've done the hard part
The brand logo next to your email isn't a design setting. It's a reward for DMARC enforcement, and it's locked behind the exact work most domains avoid.
Notes
Field notes on email authentication — how it works, how it breaks, and how to read what receiving servers see.
July 31, 2026
The brand logo next to your email isn't a design setting. It's a reward for DMARC enforcement, and it's locked behind the exact work most domains avoid.
July 31, 2026
Google, Yahoo, and now Microsoft require SPF, DKIM, and DMARC from bulk senders. As of 2025 this is no longer a best practice — it is the entry ticket to the inbox.
July 31, 2026
DKIM can be published, valid, and cryptographically perfect, and your mail can still fail DMARC because of it. The reason is almost never the signature. It's alignment.
July 31, 2026
Migrations are planned as a clean weekend cutover. Reality is a coexistence window where two mail systems run at once — and authentication has to cover both without breaking either.
July 31, 2026
A missing or generic reverse-DNS record gets mail rejected or spam-foldered — and it's the one authentication signal that doesn't live in your domain's zone, so editing your DNS won't touch it.
July 31, 2026
Once you publish a rua address, mailbox providers start sending you daily DMARC reports. They arrive as XML, so almost nobody reads them — and they're the only complete list of who sends mail as you.
July 20, 2026
A mailbox migration moves your mail. It does not move your authentication — and that gap is where deliverability quietly fails.
July 13, 2026
Most domains with DMARC are sitting on p=none, which blocks nothing. Having the record and being protected are two different states.
July 6, 2026
An SPF record can be perfectly valid and still do nothing. The reason is a limit almost no free checker counts: ten DNS lookups.