Skip to content
SpoofKiller
Troubleshooting

Email Deliverability Troubleshooting: A Working Checklist

Mail going to spam or vanishing? Work through authentication, reputation, and content in an order that finds the cause.

Reading time
7 min read
Last updated
Updated
An analyst's desk seen from above, with printed charts, a magnifying glass, and a stack of envelopes.
Start with the evidence on the desk: the bounce message and the headers. Guesswork comes last, if at all.
In this guideShow 8 sections

The first sign is never a bounce. It is a customer on the phone saying, “I never got it.” Then a second customer. Then someone in sales forwards a screenshot of your proposal sitting in a spam folder between a miracle supplement and a prince with a banking problem.

The usual response is to rewrite the subject line. This is like repainting a car that will not start. Spam filters weigh many things, and wording is near the bottom of the list. Troubleshooting works when you check the causes in order of likelihood and stop when you find one. This is that order.

Step 0: Get evidence before you change anything

“Our email is going to spam” is a rumor. Turn it into facts:

  • Which mail? Everything, or only the newsletter? One-to-one messages and bulk campaigns usually travel through different systems and fail for different reasons.
  • Which recipients? One mailbox provider, or all of them? One company, or many?
  • Since when? Sudden failures follow a change. Find the change.
  • What happens, exactly? Bounced, sent to spam, or accepted and never seen?

If a message bounced, read the bounce. The code tells you which half of this guide to read:

ResponseMeaningWhere to look
4xx (such as 421, 451)Temporary refusal; the sender will retryRate limits, reputation, greylisting
5xx mentioning authentication, SPF, DKIM, or DMARCRefused for failing authenticationStep 1
5xx mentioning a blocklist or policyThe sending IP or domain is listedStep 2
5xx user unknownThe address does not existStep 3

If the message arrived in spam, get a copy with its full headers. Paste them into the email header analyzer. The Authentication-Results header is the receiver’s own account of what it checked and what it concluded. It is the closest thing to a confession you will get.

Step 1: Authentication

Start here because it is the most common cause, the most checkable, and the one entirely within your control. In the headers you want all three of these:

Authentication-Results: mx.receiver.example;
    spf=pass smtp.mailfrom=bounces.example.com;
    dkim=pass header.d=example.com;
    dmarc=pass header.from=example.com

What each failure means:

  • spf=fail, softfail, or permerror: the sending server is not in your record, or the record is broken. See Common SPF Errors and test with the SPF checker.
  • dkim=fail or none: a missing key, a wrong selector, or a message modified after signing. See Common DKIM Errors.
  • dmarc=fail with SPF and DKIM passing: an alignment problem. The checks passed for your provider’s domain, not yours. See DMARC Alignment Explained.
  • No DMARC result at all: you have no DMARC record. Large mailbox providers now expect one from anyone sending in volume.

For a view of the whole domain and not one message, run the domain health check. If only one mail stream is affected, test a message from that stream. Staff mail can be perfectly authenticated while the newsletter platform signs as someone else.

Stop here if you found a failure. Fix it, wait a few days, and see whether placement improves before going further.

Step 2: Reputation and blocklists

Authentication proves who you are. Reputation is what receivers think of you once they know. A fully authenticated sender with a poor history goes to spam with complete cryptographic certainty.

Reputation attaches to two things: the sending IP address and the sending domain. Check both.

  • Blocklists. Look up your sending IPs and domain on the major lists. A listing on a widely used one produces immediate refusals. Each list publishes its own removal process; follow it only after fixing whatever caused the listing, or you will be back.
  • Shared addresses. On an email platform’s shared pool, your neighbors’ conduct affects your delivery. If the pool is the problem, the platform must fix it, or you move.
  • Sudden volume. A new IP or domain with no history, or a list three times its usual size sent in one morning, looks like a compromised account. Increase volume gradually.
  • Provider dashboards. Large mailbox providers offer free postmaster tools that show how they rate your domain and your complaint rate. If a single provider is the problem, its dashboard is the best evidence available.

Listings tend to be discovered late, by customers. SpoofKiller’s blacklist monitoring checks your sending IPs and domain against reputable lists daily and alerts you when one appears.

One more cause belongs here. If someone else is forging your domain and you have no enforced DMARC policy, their mail can stain your domain’s name. How to Prevent Email Spoofing covers the remedy.

Step 3: List hygiene and complaints

The strongest signal a receiver has is what its own users do. When recipients press the spam button, that is a complaint, and nothing damages a sender faster. The publicly stated guidance from the large mailbox providers is plain: keep your spam complaint rate under 0.3 percent, and aim to stay below 0.1 percent. That is three complaints per thousand messages as the ceiling, and one as the goal.

Complaints and bounces come from the list, so fix the list:

  • Send only to people who asked. Purchased and scraped lists contain uninterested strangers and trap addresses that exist to catch senders who use them.
  • Confirm new signups with a confirmation email, which keeps typos and malicious submissions off the list.
  • Remove hard bounces at once. Repeatedly mailing addresses that do not exist marks you as careless.
  • Retire the unresponsive. Someone who has not opened anything in a year is likelier to complain than to buy.
  • Make leaving easy. A reader who cannot find the unsubscribe link will use the spam button. It is always easy to find.

The unsubscribe link is not where you lose a customer. It is where you avoid a complaint from someone you had already lost.

Step 4: The bulk-sender requirements

Google and Yahoo publish requirements for those who send in bulk to their users. They are public, they are enforced, and failing them is now a common cause of trouble. In summary:

RequirementWhat it means in practice
AuthenticateSPF and DKIM on your mail, a DMARC record published (at least p=none), and a From domain that aligns
One-click unsubscribeMarketing mail carries List-Unsubscribe and List-Unsubscribe-Post headers, and requests are honored promptly
Low complaint rateStay under 0.3 percent; aim below 0.1 percent
Sound infrastructureValid reverse DNS and TLS for transmission

The one-click headers look like this:

List-Unsubscribe: <https://example.com/unsubscribe?id=abc123>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

Reputable email platforms add them for you when the feature is switched on. Check a real message. If the headers are absent, that is your answer.

Step 5: Content

Only now consider the message itself. Content matters less than folklore suggests, and it matters most when your reputation is thin. Check for:

  • Links to poorly regarded domains, including public link shorteners and tracking domains shared with strangers.
  • Mismatched links, where the visible text shows one address and the destination is another. This is what phishing looks like, and filters know it.
  • A single large image with little text, a format favored by people with something to hide.
  • Broken HTML and a missing plain-text alternative.
  • Unexpected attachments, particularly archives and documents with macros.

A simple test isolates content from everything else: send a short plain-text message through the same system to the same recipient. If it arrives in the inbox and the campaign does not, the difference is in the content. If both go to spam, it is not.

Step 6: Infrastructure

If you run your own mail server, or relay through one, verify the plumbing. Hosted platforms handle this for you.

  • Reverse DNS (PTR). The sending IP should resolve to a hostname, and that hostname should resolve back to the same IP. Addresses with no PTR record, or a generic one from an internet provider, are widely distrusted.
  • HELO name. The server should introduce itself with a real, resolvable hostname, ideally the one in its PTR record. Not localhost.
  • TLS. Offer encryption when sending. Large receivers expect it and mark mail sent without it.
  • MX records. A sending domain that cannot receive mail looks abandoned. Confirm yours with the MX lookup, and review the rest with the DNS security checker.

Then make it stay fixed

Recovery is slower than damage. Fix the cause, send your best mail to your most engaged readers first, and expect placement to improve over days or weeks. Receivers revise their opinion gradually and do not announce it.

Most deliverability emergencies start as small, silent failures: a DKIM key removed, an SPF record pushed past its limit, a listing nobody saw. DMARC monitoring shows authentication results across all your senders, and the alerts documentation explains what SpoofKiller will tell you and when. It cannot make anyone want your newsletter. It can make sure that authentication is never the reason they did not see it.

FAQ

Questions about Deliverability Troubleshooting

Short answers to what readers ask next. If yours is missing, write to us and a person will reply.

Ask a question

Free, no obligation

Want a second pair of eyes on your records?

Send us your domain. We will look at its DMARC, SPF, and DKIM setup and write back, in plain English, with what we found and what to fix first.

  • A person reads your records, not a script
  • Specific fixes, in order of importance
  • No sales sequence afterward

We use your details to reply. Nothing else.

Reading about it is the slow way.

Run the free check and see your own domain's DMARC, SPF, and DKIM in the time it took to read this paragraph. No account, no card.