All articlesDeliverability

The Complete Email Deliverability Checklist for 2025

Everything that decides whether your email reaches the inbox — authentication, infrastructure, list hygiene, content, engagement and monitoring — in one actionable checklist.

The SMTPTester Team November 22, 2025 17 min read

Delivery is not deliverability

These two words get used interchangeably and they mean very different things.

Delivery is whether the receiving server accepted your message. A 250 OK means delivered. Deliverability is whether that accepted message landed in the inbox rather than the spam folder or a silent black hole. You can have 99.8 percent delivery and terrible deliverability at the same time, and nothing in your SMTP logs will tell you.

This checklist covers every lever that moves the second number. Work through it in order; the earlier sections are prerequisites for the later ones.

1. Authentication foundation

  • [ ] SPF published as a single TXT record, under ten DNS lookups, ending in -all.
  • [ ] DKIM enabled with a 2048-bit key, signing with your own domain in the d= tag.
  • [ ] DMARC published, moving from p=none to p=reject once reports are clean.
  • [ ] Alignment verified — SPF and DKIM must align with the visible From domain, not just pass.
  • [ ] Custom return path configured so the envelope sender is a subdomain you own.
  • [ ] Parked domains protected with v=spf1 -all and p=reject.
  • [ ] MTA-STS and TLS-RPT published for mature setups.

Gmail, Yahoo and Outlook all enforce authentication for bulk senders. Failing any of the first four items caps your deliverability no matter how good your content is.

2. Infrastructure and DNS

  • [ ] Reverse DNS (PTR) on every sending IP, matching the EHLO hostname.
  • [ ] Forward-confirmed reverse DNS — the hostname resolves back to the same IP.
  • [ ] Valid A record for the sending hostname.
  • [ ] MX record on the sending domain, even if you never receive mail there. Some filters reject domains with no MX.
  • [ ] TLS on all connections, TLS 1.2 minimum, valid unexpired certificate.
  • [ ] Dedicated IP if you send more than roughly 100,000 messages a month; shared pools are better below that because volume builds reputation faster.
  • [ ] Separate subdomains for transactional and marketing streams.

The subdomain split is the highest-leverage infrastructure decision on this list. Send receipts from mail.yourdomain.com and campaigns from news.yourdomain.com. A bad marketing week then cannot push password resets into spam.

3. Reputation management

Mailbox providers score both your domain reputation and your IP reputation. Domain reputation matters more and follows you across providers; IP reputation resets if you move.

  • [ ] Warm up new IPs and domains over 4–6 weeks, starting at 50–100 messages a day.
  • [ ] Send to engaged recipients first during warm-up.
  • [ ] Maintain consistent volume. Sudden spikes look like a compromised account. A 10x jump on a Tuesday will get throttled.
  • [ ] Monitor blocklists — Spamhaus, SpamCop, Barracuda, SORBS.
  • [ ] Enrol in feedback loops with the major providers so complaints reach you.
  • [ ] Register for Google Postmaster Tools and Microsoft SNDS. Both are free and show you data you cannot get any other way.

Typical warm-up curve: 100 on day one, 500 by day four, 2,000 by day eight, 10,000 by day twelve, 50,000 by day twenty, full volume after day twenty-five.

4. List hygiene

Poor list quality causes more spam-foldering than any other single factor.

  • [ ] Confirmed opt-in for marketing lists. It costs you subscribers and saves your reputation.
  • [ ] Never buy or rent lists. Purchased lists contain spam traps, and a single pristine trap hit can blocklist a domain.
  • [ ] Validate addresses at signup — syntax, MX existence, disposable-domain detection.
  • [ ] Suppress hard bounces immediately and permanently.
  • [ ] Remove role addresses like info@, sales@, admin@ from marketing sends.
  • [ ] Sunset inactive subscribers. No opens in 6–12 months means stop sending, after one re-engagement attempt.
  • [ ] Deduplicate across lists so nobody receives the same campaign twice.

Two types of spam trap matter. Pristine traps are addresses never used by a human, published to catch scrapers — hitting one implies you did not collect the address legitimately. Recycled traps are abandoned mailboxes that a provider reactivates as traps — hitting one implies you do not remove inactive subscribers. Sunsetting protects you from the second kind.

Target thresholds: hard bounce rate below 2 percent, complaint rate below 0.1 percent (Gmail's hard limit is 0.3 percent), unsubscribe rate below 0.5 percent.

5. Message construction

  • [ ] Multipart/alternative — always include a plain-text version alongside HTML.
  • [ ] Under 100 KB of HTML; Gmail clips heavier messages and clipping hurts engagement.
  • [ ] Balanced text-to-image ratio. An email that is one large image is a classic spam signature.
  • [ ] Alt text on every image, since many clients block images by default.
  • [ ] A real From name and address. Avoid noreply@ — it discourages replies, and replies are a strong positive engagement signal.
  • [ ] List-Unsubscribe and List-Unsubscribe-Post headers on all bulk mail. One-click unsubscribe is now mandatory for bulk senders.
  • [ ] Working unsubscribe link in the body that takes at most two clicks.
  • [ ] Physical postal address in the footer where CAN-SPAM or similar law applies.
  • [ ] Tested rendering across Gmail, Outlook, Apple Mail, and mobile.

Avoid URL shorteners: they are heavily abused and filters treat them with suspicion. Host your links on a subdomain of your sending domain, and make sure that domain is not itself on a blocklist.

6. Subject lines and content signals

Modern filters use machine learning over engagement, not a keyword blacklist, so the old "never write FREE" advice is outdated. What still hurts:

  • ALL CAPS SUBJECT LINES and excessive exclamation marks.
  • Misleading subjects that do not match the body — this is a legal violation as well as a filter trigger.
  • Excessive emoji.
  • Deceptive "Re:" or "Fwd:" prefixes on messages that are neither.
  • Hidden text, white-on-white content, or invisible tracking abuse.

What helps: subject lines between 30 and 50 characters, a useful preheader, personalisation that is genuinely relevant, and a single obvious call to action.

7. Engagement

Engagement is the strongest modern deliverability signal. Providers watch opens, clicks, replies, forwards, marking as not-spam, and moving out of spam — and equally, deletions without opening, marking as spam, and ignoring.

  • [ ] Segment by engagement level and send more frequently to your most engaged, less to the rest.
  • [ ] Ask for a reply in onboarding messages; a reply is the single strongest positive signal.
  • [ ] Prompt new subscribers to add you to their contacts.
  • [ ] Let subscribers choose frequency rather than forcing them to unsubscribe entirely.
  • [ ] Respect time zones and send at a consistent cadence.

8. Monitoring and testing

  • [ ] Google Postmaster Tools — domain and IP reputation, spam rate, authentication rate.
  • [ ] Microsoft SNDS — complaint data for Outlook and Hotmail.
  • [ ] DMARC aggregate reports parsed continuously, not read once.
  • [ ] Seed list testing across the major providers before large campaigns.
  • [ ] Bounce and complaint webhooks wired into your suppression list automatically.
  • [ ] SMTP connection monitoring — an hourly synthetic authentication check catches expired credentials before customers do.
  • [ ] Alerting on bounce rate above 3 percent, complaint rate above 0.1 percent, or any drop in authentication pass rate.

9. Compliance

  • [ ] CAN-SPAM (US): accurate headers, honest subject, physical address, unsubscribe honoured within 10 business days.
  • [ ] GDPR (EU): lawful basis for processing, explicit consent for marketing, records of consent, easy withdrawal.
  • [ ] CASL (Canada): express or implied consent, sender identification, working unsubscribe.
  • [ ] Data retention policy so you are not storing subscriber data indefinitely.

Compliance and deliverability reinforce each other. Every requirement above also reduces complaints.

10. Incident response

When deliverability drops, work the diagnosis in this order:

  1. Check authentication first. An expired DKIM key or a broken SPF record explains most sudden cliffs.
  2. Check blocklists for your domain and every sending IP.
  3. Check Postmaster Tools for a reputation change and a spam-rate spike.
  4. Look for a volume anomaly in the preceding week.
  5. Review recent content changes — a new template, a new link domain, a new tracking pixel.
  6. Isolate the provider. If only Gmail is affected, it is engagement or Gmail-specific policy. If everyone is affected, it is authentication or infrastructure.
  7. Pause non-essential sending while you fix the cause, and resume with your most engaged segment.

Do not respond to a reputation problem by sending more mail to more people. That is the reflex, and it always makes things worse.

Your weekly routine

  • Review bounce and complaint rates.
  • Scan Postmaster Tools for reputation drift.
  • Skim DMARC reports for unfamiliar sources.
  • Process new hard bounces into the suppression list.
  • Verify the SMTP relay still authenticates.
  • Check blocklists for a new listing.

Ten minutes a week prevents the multi-day outage that follows from noticing a problem a month late. Before any configuration change reaches production, confirm the transport layer still works end to end with SMTPTester — authentication, TLS negotiation, and relay in one pass.

Understanding the filters you are up against

Modern spam filtering is not a keyword scanner. It is a machine-learning system weighing hundreds of signals, and the weights differ by provider.

Gmail leans heavily on individual engagement history. If a specific recipient regularly opens your mail, it reaches their inbox even when your aggregate reputation is mediocre. If they never open it, it eventually stops reaching them regardless of how clean your setup is. Gmail also applies tabbed categorisation — Promotions is not the spam folder, and landing there is normal for marketing mail.

Microsoft weights IP reputation more heavily than Gmail and is comparatively strict about sudden volume changes. It also runs its own filtering stack for both consumer Outlook.com and corporate Microsoft 365 tenants, with different thresholds.

Yahoo and AOL share infrastructure and are unusually sensitive to complaint rates.

Corporate gateways such as Proofpoint, Mimecast and Barracuda sit in front of many business mailboxes and apply their own policies, often stricter than the mailbox provider's. Attachment types and link reputation matter more here.

The practical consequence: measure deliverability per provider, not in aggregate. A single number hides the story.

Content that quietly hurts

Beyond obvious spam signals, several technically-correct choices reduce placement:

  • Link domain mismatch. Links pointing at a domain unrelated to the sender look like a phishing pattern. Use tracking links on a subdomain of your sending domain.
  • Shared tracking domains. If your provider offers a shared click-tracking domain, its reputation is pooled with every other customer. Configure a custom tracking domain.
  • Unnecessary redirects. Multi-hop redirect chains are heavily penalised.
  • Attachments on bulk mail. Almost always a negative signal; link instead.
  • Excessive HTML nesting. Tables inside tables inside tables can trigger structural heuristics and break rendering in Outlook.
  • Broken or missing unsubscribe. A recipient who cannot unsubscribe will click "report spam" instead.

Measuring what you cannot see

The hardest part of deliverability is that inbox placement is invisible from your side. You know a message was accepted; you do not know where it landed. Three techniques help:

Seed lists. Send campaigns to a set of test mailboxes across the major providers and record where each one lands. Cheap and directional, though seed accounts have no engagement history so results skew pessimistic.

Panel data. Commercial services measure placement across a panel of real mailboxes. More accurate, and priced accordingly.

Engagement proxies. A drop in open rate for a specific provider, with no change in content or list, is strong evidence of a placement problem at that provider. This costs nothing and is often the earliest signal you get.

An operating rhythm

Deliverability degrades gradually and then fails suddenly. A calendar prevents that.

Daily: check bounce and complaint rates against thresholds; process the suppression queue.

Weekly: review Google Postmaster Tools reputation; skim DMARC reports for unknown sources; check blocklists.

Monthly: run a seed test; review engagement segments; sunset newly inactive subscribers; verify authentication records still resolve.

Quarterly: audit every third-party sender; rotate DKIM keys and SMTP credentials; review consent records; re-verify any list that has not been mailed recently.

None of these take long. The teams that keep excellent inbox rates are not doing anything exotic — they are doing ordinary things consistently, which is exactly why their reputation stays stable while everyone else's oscillates.

Test your SMTP server now

Apply what you just learned. Free, no signup, results in seconds.

Open the tool →

Continue reading