If your SPF, DKIM and DMARC all pass and your outbound email still lands in spam, the problem is not authentication. Authentication tells a receiving server that your email is really from your domain. It says nothing about whether that domain, that mailbox, or that specific message is wanted. A thread in r/gsuite lays this out well: someone running a 9 month old Google Workspace domain with every DNS record configured correctly was still getting buried in spam, and the honest answer in the comments was that passing the three checks is table stakes, not a deliverability guarantee.
This matters a lot if you send outreach from your own mailbox, which is the whole point of not routing everything through a relay or a shared sending pool. Your own domain reputation is now entirely yours to protect, for better and for worse.
Authentication Proves Identity, Not Reputation
SPF, DKIM and DMARC exist to stop spoofing. They let a receiving server confirm the message genuinely came from your domain and was not forged. That is a real and necessary layer, but it answers a narrow question: is this sender who they claim to be. It does not answer the question that actually decides inbox placement: does this sender have a history of sending mail that people open, reply to, and do not report.
Google, Microsoft and every major mailbox provider build a reputation score per sending domain and per sending IP, based on real recipient behavior over time. A domain that passes every authentication check but has no sending history, or a bad one, still gets filtered. The thread's top comment makes a useful point here: do not blame low volume alone. A brand new domain sending five emails a day is not automatically penalized for being small. It is penalized when the content, formatting or pattern of those five emails looks like the content, formatting or pattern of spam that has been reported before.
What To Check Before Blaming Warm-up
When authentication passes and deliverability is still bad, work through these before assuming you just need more time:
- Plain text rendering. HTML email with heavy styling, tracking pixels, or an image-heavy signature reads as commercial, not personal, to spam filters and to humans. Plain text, or HTML that renders close to plain text, consistently performs better for first-touch outreach.
- Link and tracking pixel density. Every link redirect through a third-party tracking domain and every open-tracking pixel is a signal spam filters weigh. A message with one or two clean links to your own domain looks different than one wrapped in a tracking layer.
- Subject line patterns. Subject lines that resemble mass-mail templates, with brackets, all caps words, or generic urgency, get flagged regardless of how clean your DNS is.
- Reply and engagement history. If nobody has ever replied to mail from this address, and a meaningful share of recipients has deleted without opening, that pattern compounds. A domain's reputation is built message by message.
- Send volume and spacing. Sending all your daily volume in one burst at 9am looks different to a filter than the same volume spread naturally across the day, which is closer to how a human actually works through their outbox.
- List quality. If your list includes guessed addresses, role addresses, or stale contacts from a purchased database, your bounce rate and spam complaint rate both rise, and both feed directly into domain reputation. This is one of the strongest reasons to build target lists from live company research rather than a bought database: every contact you add to a cold domain either helps or hurts its reputation, permanently.
Why This Is Worse on a New Domain, and Why It Still Matters on an Old One
A 9 month old domain is not new in calendar terms, but it can still be new in sending terms if it has never built up a consistent, clean sending history. Reputation is cumulative and sticky. A handful of early spam complaints or a high early bounce rate can leave a mark that takes months of clean sending to overcome, authentication notwithstanding.
This is also why ramping sending volume gradually, rather than switching a new domain straight to full daily caps, is not superstition. It gives mailbox providers a chance to observe a clean pattern before you ask them to trust you with volume.
What This Looks Like in Practice
The fix is rarely a single setting. It is a combination of sending plain, personal-looking email, from a domain with a clean history, at a pace and spacing that does not look automated, to a list built from real research rather than guesswork, with any bounce or complaint signal acted on immediately rather than ignored.
This is the exact set of defaults Eveil is built around for this reason. Sending goes out over plain SMTP from your own mailbox, with your own domain's reputation, not a shared sending pool where someone else's bad history can drag your deliverability down. Daily caps and ramp-up spread volume across the day instead of bursting it. Lists come from live company and contact discovery rather than a purchased database, which keeps bounce rates lower from the start. A bounce breaker per mailbox and circuit breakers on bounce rate, spam complaint rate and negative-reply rate pause sending automatically if any of those signals moves the wrong way, before it does lasting damage to the domain. None of that replaces good judgment about content and pacing, but it removes the most common ways people accidentally wreck a domain's reputation while chasing volume.
The Real Test
If SPF, DKIM and DMARC all pass and deliverability is still bad, stop looking at DNS and start looking at behavior: what the email looks like, how it is sent, who it goes to, and what recipients do with it. Authentication gets your email considered. Reputation, built message by message, is what gets it opened.