Email Deliverability: Why Your Emails Land in Spam

A marketing team can spend weeks on subject lines, segmentation, and send-time optimization, and still watch open rates crater — not because the email was bad, but because it never reached the inbox. Deliverability is the layer underneath all of that work, and it’s almost entirely invisible until something breaks. Most teams only start paying attention after Gmail quietly starts routing their newsletter to spam, which is the wrong time to learn how any of this works.

Deliverability isn’t one setting you turn on. It’s a combination of authentication, sending reputation, and content signals that mailbox providers evaluate on every single send. Get any one of them wrong consistently and the others stop mattering.

Authentication Is Table Stakes, Not a Nice-to-Have

SPF, DKIM, and DMARC exist to prove that a message claiming to come from your domain actually came from a server you authorized. Without them, a mailbox provider has no way to distinguish your transactional receipt from a phishing attempt spoofing your domain, and it will increasingly err on the side of not trusting either.

SPF publishes a list of servers allowed to send on your domain’s behalf. DKIM signs each message cryptographically so a receiving server can confirm it wasn’t altered in transit. DMARC tells receiving servers what to do when a message fails both — reject it, quarantine it, or just monitor — and gives you a reporting mechanism to see who’s sending mail as your domain, authorized or not. Gmail and Yahoo made DMARC enforcement mandatory for meaningful send volume back in 2024, and that bar hasn’t relaxed since. If your domain still doesn’t have a DMARC record, or has one set to p=none with nobody reading the reports, you’re flying blind on the signal mailbox providers weight most heavily.

Set all three up once, at the DNS level, and they keep working. This is the highest-leverage hour a team can spend on deliverability, and it’s the one most commonly skipped because it doesn’t feel like marketing work.

Sender Reputation Is a Score You Can’t See Directly

Every sending domain and IP accumulates a reputation with each major mailbox provider, built from bounce rates, spam complaints, engagement, and send consistency. It’s not published as a single number, but Google Postmaster Tools and Microsoft SNDS give a directional read on where you stand with the two providers that matter most.

The fastest way to damage reputation is inconsistency: a domain that sends nothing for two months and then blasts fifty thousand messages in an afternoon looks like a compromised account or a spammer testing a new list, regardless of intent. Warm up sending volume gradually on a new domain or IP, and keep cadence steady once you’re at scale.

Bounce rate and complaint rate matter more than almost anything else you can control. A hard bounce means the address doesn’t exist — keep sending to it and providers read that as a sign you’re not validating your list, which is itself a spam signal. A complaint means someone marked your mail as spam, and providers weight that far more heavily than an unsubscribe, since it’s a stronger signal about whether recipients want your mail at all. Both metrics are why unchecked list growth from questionable sources — purchased lists, scraped addresses, old contacts nobody re-engaged with — is one of the most reliable ways to tank a domain’s reputation permanently.

Engagement Signals Now Outweigh Content Filtering

Mailbox providers used to rely heavily on scanning message content for spam-like patterns: certain words, excessive links, subject-line tricks. That filtering still exists, but it’s a minor factor next to engagement — whether recipients open, read, reply to, and act on your mail. A message a meaningful share of recipients open and engage with signals wanted mail. A message that goes straight to the trash unread, repeatedly, signals the opposite, even if the copy is clean and the list is opted in.

This is why list hygiene compounds over time in a way that’s easy to underestimate. Recipients who haven’t opened anything in six months aren’t neutral — they’re dragging down your engagement rate on every send, which drags down deliverability for the recipients who do want your mail. Segmenting out or re-engaging, then removing, unengaged contacts isn’t just good list management; it’s a direct deliverability lever, often a bigger one than anything you’d change in the email itself.

Fix the Infrastructure Before You Fix the Copy

When deliverability drops, the instinct is to rewrite subject lines or change the sending tool. Sometimes that helps at the margins, but it skips the diagnosis. Check authentication status first — a broken or missing DMARC record will sink deliverability regardless of how good the email is. Check bounce and complaint rates in your ESP’s dashboard next; a spike there points to a list problem, not a copy problem. Only after ruling those out is it worth treating deliverability as a content or design issue.

Teams that keep landing in the inbox treat deliverability as ongoing infrastructure, not a one-time setup task: monitoring authentication reports, pruning unengaged contacts on a schedule, watching reputation tools the way they’d watch error rates. Teams that end up in spam treat it as invisible until a campaign underperforms, and by then the damage takes weeks of clean sending to reverse.

PNK WORKS builds and audits the email infrastructure behind marketing and product sends, from authentication to list strategy. Start a project.