An email that leaves your outbound queue successfully is not an email that reaches the inbox. Between your servers and the recipient's primary tab sit authentication checks, content filters, reputation databases and engagement scoring, and any one of them can quietly reroute months of careful work into the spam folder. The failure is silent: nothing throws an exception, open rates just slide.
This checklist is the routine to run before a big launch, after any infrastructure or DNS change, and once a quarter as a health baseline. Work through it top to bottom — each section catches failures the previous one cannot see.
Authentication: SPF, DKIM and DMARC
- Cover every sending host in SPF. List every service that sends as your domain — your own servers, the ESP, the CRM, the helpdesk. One missing include produces soft fails that some receivers treat as spam. Verify with the SPF, DKIM and DMARC checker instead of eyeballing DNS records, and watch the 10-DNS-lookup limit as the chain grows.
- Sign with DKIM using 2048-bit keys. Publish the new selector before retiring the old one so in-flight messages stay valid, and confirm the signature survives forwarding and address rewriting.
- Reach DMARC enforcement with alignment. Start at p=none with aggregate reports going to a mailbox someone actually reads, then move to quarantine and reject. Misaligned domains are the most common failure we see.
- Re-test after every DNS change. Record truncation and slow propagation break authentication invisibly. The same gremlins are behind most cases of verification codes arriving late, so treat a delayed-code report as an authentication smell.
Content and structure filters
- Render-test first. Broken templates do not spam-folder you by themselves, but they make everything after harder to diagnose. The workflow in email template testing gets rendering out of the way so filter signals are the only variable left.
- Scan for trigger patterns. All-caps subjects, deceptive punctuation, a near-zero text-to-image ratio, URL shorteners, and click-tracking domains that do not match the visible sender all add filter points.
- Validate the unsubscribe path. List-Unsubscribe headers with one-click support are table stakes at Gmail and Outlook now. A broken unsubscribe link is both a filter signal and a compliance problem.
List hygiene
- Suppress hard bounces immediately. Repeated sends to dead addresses are the fastest route to a deferral or a block, and they never convert.
- Sunset inactive recipients. Six months without a single open makes an address a liability at engagement-weighting providers. Try one re-engagement campaign, then let the silence go.
- Keep proof of consent. When a recipient reports spam to their provider, your signup logs are the only defense that matters.
Seed testing: measure placement
- Run a seed list at every major provider. Identical content, same send time, record inbox versus spam versus missing for each provider. Single runs are noisy — repeat on three days before drawing conclusions.
- Spot-check with fresh real inboxes. Seed accounts age and skew; brand-new addresses approximate the new-signup experience better. Creating disposable inboxes at several providers and watching what actually arrives is a cheap end-to-end truth check, and the technique in QA test accounts with temporary email automates it.
Bounce handling and feedback loops
- Classify every bounce. Hard bounces suppress forever; soft bounces (full mailboxes, greylisting, temporary deferrals) retry on a schedule. Blending the two corrupts your list.
- Read the headers of the survivors. When a message vanishes at one provider, the Received chain and filtering remarks usually say why — the email header analyzer decodes them.
- Wire complaints into automation. Register for feedback loops at the major providers and route bounces and complaints to a webhook. Testing that pipeline used to require real mail loops; webhook email testing shows how to exercise it end to end.
Continuous monitoring
- Check the big blocklists weekly. A Spamhaus listing explains sudden collapse like nothing else; catch it before your users do.
- Track Postmaster Tools. Domain reputation dashboards are the closest thing to ground truth at Gmail.
- Alert on placement, not on sends. Accepted-by-server counts hide spam-foldering. Alert when seed or spot-check placement drops, not when volume rises.
Run the full checklist quarterly and the diff after every change, and 2026 will not be the year your emails disappear quietly.
FAQ
How often should I run deliverability tests? Run the full checklist quarterly, plus after any DNS change, ESP migration or template redesign. Continuous monitoring fills the gaps between formal runs.
Does passing SPF, DKIM and DMARC guarantee inbox placement? No. Authentication is a cover charge, not a VIP pass — it prevents rejection and spoofing, while content, reputation and engagement decide the folder.
What is the fastest deliverability win? Suppressing hard bounces and sunsetting inactive recipients. Most reputation damage is self-inflicted by continuing to mail addresses that stopped responding.
Do seed lists work for B2B sends? Partially. Seeds cover the big consumer providers well, but corporate filters vary per installation. Ask key customers for a test address, or monitor bounces and replies closely.