Email deliverability basics: why your emails land in spam and how to fix it

A newsletter I helped troubleshoot last spring had a subscriber list of 8,000 people and an open rate hovering around 4%. That number wasn't a content problem — when we ran a seed test sending to accounts at Gmail, Outlook, and Yahoo, eleven of the twelve landed straight in spam or, worse, disappeared into the promotions tab's more aggressive filtering. The writer had assumed people just weren't interested. The actual issue was three missing DNS records and a sending pattern that looked, to every major mail provider's spam model, exactly like a compromised account blasting out mail.

The three DNS records nobody explains simply

SPF (Sender Policy Framework) is a DNS record listing which mail servers are allowed to send email claiming to be from your domain — without it, receiving servers have no way to confirm your mail isn't forged. DKIM (DomainKeys Identified Mail) attaches a cryptographic signature to each outgoing message so the receiving server can verify the content wasn't altered in transit and genuinely came from a server you authorized. DMARC (Domain-based Message Authentication) tells receiving servers what to do when a message fails SPF or DKIM checks — quarantine it, reject it outright, or do nothing — and it's the record most small senders skip entirely, which is often the single biggest deliverability gap on a young domain.

Why a brand-new domain gets penalized by default

Mail providers have no sending history to judge a fresh domain against, so they default to caution, and a domain that suddenly sends 8,000 emails on day one looks statistically identical to a spam operation ramping up. This is why domain age and sending reputation matter as much as the technical records: a domain registered last week, with all three DNS records perfectly configured, will still see worse inbox placement than a two-year-old domain with an established, consistent sending pattern.

Warming up a domain properly

The fix is a gradual ramp: start by sending to your most engaged subscribers only — the ones who've opened and clicked recently — in batches of a few hundred a day, increasing volume over two to three weeks rather than blasting the full list immediately. Mail providers track engagement signals like open rate, reply rate, and how often recipients mark a sender as spam, and a slow ramp with strong early engagement builds exactly the reputation signal that earns inbox placement for the full list later.

Content triggers that still matter in 2026

Spam filtering has moved well past simple keyword blocking, but certain patterns still correlate strongly with poor placement: an image-only email with almost no actual text, a subject line in all caps or stacked with exclamation points, a mismatch between the display name and the sending domain, and links that route through several redirect hops before reaching the final destination. None of these alone guarantees a spam folder, but stacking two or three of them on a domain that's still building reputation is a common, avoidable cause of a bad month.

List hygiene is deliverability, not just tidiness

A list padded with old, unengaged addresses drags down your aggregate engagement metrics, which providers weigh heavily when deciding where to route your next campaign. Removing subscribers who haven't opened anything in six-plus months, immediately suppressing hard bounces, and never buying or scraping a list are the highest-leverage list-hygiene moves, because a smaller list of people who actually open your mail produces a far stronger sender reputation than a larger list padded with dead addresses.

Reading a bounce message instead of ignoring it

A hard bounce (permanent failure — the address doesn't exist) needs immediate suppression from future sends, while a soft bounce (temporary — mailbox full, server briefly down) can be retried a limited number of times before also being suppressed if it persists. Most sending platforms categorize this automatically, but if you're managing anything manually, treating every bounce the same way — retrying indefinitely — is one of the fastest ways to get your sending IP or domain flagged.

Practical tools that help along the way

Before you touch DNS, run your planned sender domain and any campaign links through a URL encoder or decoder if you're building tracking parameters manually, since malformed query strings in tracking links are a surprisingly common cause of links looking suspicious to filters. A UTM link builder keeps your campaign tracking consistent and human-readable rather than a jumble of encoded characters, which also reads better to both spam filters and actual recipients previewing a link before clicking. And if you're auditing subject lines at scale for repeated phrasing that might read as spammy, a word frequency counter run across your last twenty campaigns will surface overused patterns faster than eyeballing them one by one.

Deliverability questions people ask after a bad send

I set up SPF and DKIM correctly but I'm still landing in spam — why? Authentication only proves you are who you say you are; it doesn't guarantee good placement on its own, and a new domain with low engagement can still land in spam even with perfect records while reputation builds.

Does sending from a subdomain instead of the root domain help? Yes, using a dedicated subdomain for marketing mail isolates that sending reputation from your transactional or personal email on the root domain, so a bad campaign doesn't drag down every other kind of mail you send.

How fast can a damaged sender reputation recover? Recovery is typically measured in weeks to a couple of months of consistent, well-targeted, low-complaint sending — there's no instant fix once major providers have flagged a domain or IP.

Do unsubscribe links actually help deliverability? Yes, a clear, one-click unsubscribe reduces spam complaints because frustrated recipients who can't easily opt out often mark mail as spam instead, which is a far worse signal to your sender reputation than a clean unsubscribe.

Putting the checklist together

In practice, the fix for that 4%-open newsletter was mechanical rather than creative: publish correct SPF, DKIM, and DMARC records, split the list into an engaged segment for a two-week warm-up, prune anything unopened in the last eight months, and rebuild every tracking link with a proper UTM builder instead of hand-typed query strings that had accumulated small formatting errors over a year of ad hoc edits. Six weeks later the same content, sent to a smaller but properly warmed list, was landing at a 94% inbox placement rate in seed testing, and open rates on the newsletter settled around 38% — not because the writing changed, but because the mail was finally arriving where it was supposed to.

The long-term maintenance nobody budgets for

Deliverability isn't a one-time setup; DNS records need occasional revisiting after a provider migration, DMARC reports should be checked periodically for unauthorized senders spoofing your domain, and engagement-based list pruning works best as a recurring quarterly habit rather than a one-off cleanup. Treat your sending domain the way you'd treat any other piece of infrastructure that quietly stops working if nobody checks on it.