---
title: "Discussion on \"SPF, DKIM and DMARC all passed. Gmail still sent my mail to spam.\" | Hashnode"
description: "Discussion on \"SPF, DKIM and DMARC all passed. Gmail still sent my mail to spam.\". Every guide says to fix your authentication first. Mine was already perfect, and my domain's mail still landed in Gmail spam through four different sending routes. What I found, what I changed, and how it came back to the inbox on September 1st."
url: "https://hashnode.com/posts/spf-dkim-and-dmarc-all-passed-gmail-still-sent-my-mail-to-spam/6abfca357047004713ea9c84"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [SPF, DKIM and DMARC all passed. Gmail still sent my mail to spam.](https://hisashi.hashnode.dev/spf-dkim-and-dmarc-all-passed-gmail-still-sent-my-mail-to-spam?utm_source=hashnode&utm_medium=feed)

Every guide says to fix your authentication first. Mine was already perfect, and my domain's mail still landed in Gmail spam through four different sending routes. What I found, what I changed, and how it came back to the inbox on September 1st.

Oct 2 · 3 min read · hisashi.hashnode.dev  
Read the article

-   [#email](https://hashnode.com/tag/email)
-   [#gmail](https://hashnode.com/tag/gmail)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Hisashi Hirajo](https://hashnode.com/@hirajo)

@hirajo

  
[View profile](https://hashnode.com/@hirajo)

## Responses 2

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/spf-dkim-and-dmarc-all-passed-gmail-still-sent-my-mail-to-spam/6abfca357047004713ea9c84/comment/6ad2915c713b35d1a417b289)

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.

[Hisashi Hirajo](https://hashnode.com/@hirajo)

[Oct 18](https://hashnode.com/posts/spf-dkim-and-dmarc-all-passed-gmail-still-sent-my-mail-to-spam/6abfca357047004713ea9c84/comment/6ad2915c713b35d1a417b289#reply-6ad4af949c4b0ecb483195dd)

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.