Home

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "SPF, DKIM and DMARC all passed. Gmail still sent my mail to spam." | Hashnode

Feed/

Discussion

Hisashi Hirajo

Oct 2

SPF, DKIM and DMARC all passed. Gmail still sent my mail to spam.

Ask anyone why their email is going to spam and the first answer is always the same: check SPF, DKIM and DMARC. It's good advice. It's also where most guides stop. In August 2026, mail from my own dom

hisashi.hashnode.dev3 min read

#email #gmail #webdev #devops

Responses2

Markdown supported · ⌘↵ to post

StackShortlist

Proof Over Promises.

The forgotten warm-up service still sending 40 emails a day from the old server is such an easy thing to miss after a migration, and the same-week test to 1,783 people from a second address is a clean way to rule out content. I also appreciate that you said plainly you can't separate the warm-up change from the reply-based giveaway. If you ever test it again, sending the reply campaign from a fresh subdomain first might help isolate which one Gmail responded to.

6d ago

Hisashi Hirajo

4d ago

Thanks for reading it that closely. That warm-up was easy to miss because nothing looked broken on my end. Every message still passed authentication.

The subdomain idea makes sense. I didn't split it because once I'd found the warm-up still sending from a server nobody was reading, the cause was clear enough, and I haven't had a reason to rerun it. Opens from Gmail users were 0.2% in August and about 20% in early October.