/ Learn — Deliverability
Why emails go to spam: a symptom with several causes.
Mail in the spam folder looks the same no matter what put it there — but it has a handful of distinct causes, and the right fix depends entirely on which one is yours. This guide names the causes, shows you how to tell them apart, and routes you to the fix for each, so you diagnose before you change anything.
/ In short
Email goes to spam for a handful of distinct reasons: authentication gaps (SPF, DKIM, DMARC failing or unaligned), poor reputation (from complaints, bounces, or trap hits), blocklist listings, poor list hygiene, unwanted mail drawing complaints, unwarmed sending or volume spikes, and — less often than people think — problematic content. Because the symptom is identical whatever the cause, the key is to diagnose in order: check authentication first (common and fixable), then reputation, then blocklists, then list hygiene and complaints, then history and content. Fix the cause you actually have — changing things before diagnosing usually wastes effort on the wrong one.
/ 01 — A symptom, not a diagnosis
"In spam" is the fever. It is not the illness.
The most common mistake with spam placement is treating it as a single problem with a single fix. It is not. "My email goes to spam" describes a symptom, and that symptom is produced by several quite different underlying causes — an authentication gap, a damaged reputation, a blocklist listing, a dirty list, unwanted mail, an unwarmed sender, occasionally the content itself. They all present identically, as mail in the spam folder, which is exactly why they get confused and why generic advice so often fails to help.
Because the causes are different, the fixes are different — and a fix aimed at the wrong cause does nothing while costing you time. Tightening your authentication does not help if the real problem is a complaint-driven reputation collapse; rewriting your subject lines does nothing if you are on a blocklist; warming an IP is pointless if your DMARC is misaligned. The single most valuable habit in dealing with spam placement is to diagnose first and change second, because the symptom alone tells you almost nothing about which lever to pull.
So this guide is built as a diagnosis rather than a list of tips. The sections that follow name each cause, show the signal that distinguishes it from the others, and point to the specific fix — usually a dedicated guide where that one cause is treated in depth. The interactive diagnoser narrows it from your symptoms, and the diagnostic order at the end gives you a repeatable sequence. The aim throughout is to get you to the one cause that is actually yours before you spend effort on the others. That single discipline — diagnose, then fix — is what separates a quick recovery from weeks of frustrated guessing, because the spam folder is unusually good at hiding which of its several causes is the one currently affecting you. Treat the symptom as a question to investigate, not an answer to act on.
/ 02 — One symptom, several roots
The same spam folder, reached by different roads.
/ 03 — The spam diagnoser
Which one sounds like you?
/ 04 — The causes, told apart
Each cause, the signal that reveals it, and where the fix lives.
Authentication gaps. If SPF, DKIM, or DMARC fail or are unaligned, providers cannot confirm the mail is really from you, and increasingly route it to spam — the tightened Gmail and Yahoo bulk-sender rules made this sharper. The signal is in a message's Authentication-Results header and your Postmaster Tools data. It is the most common and most fixable cause, with the full method in the email authentication guide.
Poor reputation. If authentication is clean but mail still lands in spam, the cause is usually reputation — the accumulated judgment built from complaints, bounces, and trap hits. The signal is a Bad or Low domain reputation in Postmaster Tools. Reputation is slower to repair than configuration, and the sender reputation guide covers building and rebuilding it.
Blocklists, hygiene, and complaints. A blocklist listing causes immediate, widespread spam placement — look your IPs and domains up on Spamhaus and others. Poor list hygiene shows as a bounce rate past a few percent, and unwanted mail shows as a complaint rate above roughly 0.1 to 0.3 percent; both are fixed at the source, with verification at signup covered in the email verification page.
Unwarmed sending, spikes, and content. A brand-new IP or domain with no history, or a sudden volume spike, reads as risky and gets filtered until trust is built — the IP warming guide has the schedules. Content is the last and usually smallest factor: broken HTML, image-only mail, misleading subjects, or links to poor-reputation domains can hurt, but only check it once the larger causes are ruled out, since modern filters weight reputation far above keywords. The reason content sits last is not that it never matters — it is that the time spent rewriting an email is wasted if the message would have been filtered no matter what it said. Rule out the causes you cannot see in the email before scrutinising the one you can, because the visible thing is rarely the culprit.
/ 05 — Myths that send you down the wrong road
The popular fixes are usually the wrong ones.
“It's the spam words.” The belief that a word like “free” or an exclamation mark dooms an email is mostly a relic. Modern filters weight sender reputation and engagement far above keyword matching, so a trusted sender can write “free” all day and reach the inbox, while a distrusted one lands in spam with the most careful copy. Chasing trigger words sends you rewriting subject lines when the real lever is almost always reputation or authentication.
“Switching providers will fix it.” Tempting, and usually wrong, because the things that cause spam placement mostly follow you. Domain reputation travels with your domain regardless of who sends the mail; list practices and consent problems move with your list. Change platforms without fixing the underlying cause and you tend to reproduce the same result on new infrastructure a few weeks later. A move helps only when your current setup is itself the cause — a shared IP with bad neighbors, no stream separation — and even then the fix is the isolation, not the logo.
“It must be the design.” Content and design are real factors, but the smallest ones, and obsessing over them is the classic way to spend weeks fixing the wrong thing. A beautifully redesigned template still lands in spam if your DMARC is misaligned or your reputation is shot. The honest order is to treat content as the last suspect, examined only once authentication, reputation, blocklists, and hygiene are ruled out — not the first, however satisfying it feels to rewrite an email you can see. There is a pattern across all three myths: each one points you at something tangible and immediate — a word, a platform, a design — and away from the less visible causes that actually drive spam placement. The tangible fix feels like progress, which is exactly what makes these myths durable. The discipline is to resist the satisfying-but-wrong move and check the boring, invisible fundamentals first.
/ 06 — Diagnose in order
A repeatable sequence, common-and-fixable first.
The order matters: it runs from the causes that are most common and quickest to fix toward the more diffuse ones, and each step either finds your problem or cleanly rules a cause out.
- 1 — Authentication. Confirm SPF, DKIM, and DMARC pass and align, in message headers and Postmaster Tools. Common, high-impact, and the fastest to fix when it is the cause.
- 2 — Reputation. Check domain and IP reputation in Postmaster Tools. A Bad or Low rating points at complaints, bounces, or traps as the driver.
- 3 — Blocklists. Look your IPs and domains up on Spamhaus and major lists. A listing explains sudden, widespread spam placement and has its own delisting path.
- 4 — Hygiene and complaints. Review bounce rate and complaint rate. Past a few percent bounces, or above ~0.1–0.3% complaints, identifies list or consent problems.
- 5 — History and content. Is sending new or unwarmed? Did volume spike? Is it one campaign? These pin down intermittent or campaign-specific issues — and only here does content come into scope.
/ 07 — Where EDP fits
Most of these causes are operational — and preventable.
Look down the list of causes and a pattern appears: nearly all of them are operational rather than accidental. Authentication has to be set up aligned and kept that way; reputation has to be built and watched; lists have to be cleaned; new IPs have to be warmed; streams have to be separated so one kind of mail cannot drag down another. None of it is mysterious, but all of it is ongoing work that is easy to under-resource — which is how most senders end up in the spam folder in the first place.
That is the shape of what EDP runs. Sending happens on dedicated IPs you own, on EDP's own PowerMTA and KumoMTA, with authentication set up aligned, streams separated, warming handled on the right schedule, and reputation monitored as a managed service — so the operational causes on this page are being prevented continuously rather than diagnosed after the fact. The diagnosis on this page is what you do when mail is already in spam; managed infrastructure is how you keep most of these causes from arising at all, which is the cheaper side of the same problem. The asymmetry is the whole argument: diagnosing and repairing spam placement after the fact costs lost mail, support load, and the slow grind of rebuilding reputation, while the operational discipline that prevents it costs only that it be done consistently by someone whose job it is. Most senders end up in spam not because the prevention is hard but because it is nobody's dedicated responsibility — which is precisely the gap a managed service closes.
/ 08 — Questions
Spam placement, answered.
Why are my emails going to spam all of a sudden?
A sudden change almost always points to reputation or a blocklist rather than configuration, because configuration problems are usually present from the start. The common triggers are a volume spike that looked like compromise or list-buying, a send to an old unengaged segment that generated a wave of complaints, a batch of hard bounces from a stale list, or a spam-trap hit that landed you on a blocklist. The diagnostic move is to check your reputation in Google Postmaster Tools and look yourself up on major blocklists; a recent drop in reputation or a fresh listing will usually explain a sudden change, and points you at which underlying behavior to correct.
Do authentication problems really send email to spam?
Yes, and they are among the most common causes — especially since Gmail and Yahoo tightened their bulk-sender requirements to expect proper SPF, DKIM, and DMARC. When a provider cannot confirm a message is genuinely from who it claims to be, it has every reason to treat it as suspicious and route it to spam. The good news is that authentication is the most fixable cause: it is a configuration issue with a definite right answer, unlike reputation which takes time to rebuild. This is exactly why authentication is the first thing to check — it is common, it is high-impact, and when it is the problem, it is the fastest to resolve.
Can the content of my email cause spam placement?
It can, but it is usually a smaller factor than senders assume, and it is rarely the whole story. Modern filters weight sender reputation and engagement far more heavily than keyword matching, so the myth that a single word like 'free' dooms an email is mostly outdated. That said, genuinely problematic content still hurts: broken HTML, an image-only email with no text, misleading subject lines, links to poor-reputation domains, or content that consistently draws complaints. If your authentication and reputation are clean and a specific campaign still lands in spam, content is worth examining — but check the bigger levers first.
How do I know which cause is mine?
By checking in a deliberate order rather than guessing, because the symptom — mail in spam — looks identical regardless of cause. Start with authentication, since it is common and definitively checkable in message headers and Postmaster Tools. Then reputation, then blocklists, then list hygiene and complaint rates, then sending history and content. This order works because it goes from the most common and most fixable causes to the more diffuse ones, and because each check either identifies your problem or cleanly rules a cause out. The mistake to avoid is changing things before diagnosing, which can mask the real cause and waste effort on the wrong fix.
Will switching email providers fix my spam problem?
Usually not on its own, because most spam placement is caused by your reputation, authentication, and list practices, all of which largely follow you. Domain reputation in particular travels with your domain regardless of which provider sends the mail, so moving platforms without fixing the underlying cause tends to reproduce the same problem on new infrastructure. Where a move genuinely helps is when the cause is your current setup itself — a shared IP with bad neighbors, an inability to properly separate streams, or a provider that does not support the authentication and warming you need. In those cases the move is part of the fix, but the fix is still really about reputation, isolation, and authentication, regardless of which platform sends the mail.
How long does it take to get out of spam once I fix the cause?
It depends on the cause. An authentication fix can take effect within a sending cycle or two once the corrected records propagate, because nothing has to be rebuilt — the configuration simply becomes right. A reputation problem is slower, because reputation recovers only as providers observe a sustained pattern of good sending, which generally takes weeks rather than days. A blocklist listing clears on the blocklist's own timeline once you have fixed the cause and requested delisting. The honest summary is that the configuration causes resolve quickly and the reputation causes resolve slowly, which is one more reason to diagnose precisely rather than hoping a single change fixes everything at once.
Is my mail in spam, or being blocked entirely?
These are different problems with different signals, and worth telling apart before you diagnose. Spam placement means the mail was accepted and filed in the spam folder — the recipient could still find it, and you get no bounce, which is why it is so easy to miss. A block or outright rejection means the receiving server refused the message, which appears in your logs as a bounce with an SMTP error, often citing a blocklist or a policy reason. A deferral or greylisting is a third case: a temporary ‘try again later’ that usually clears on retry. Your bounce logs are the tell — silent spam-foldering leaves no trace there, while blocks and deferrals announce themselves in the SMTP response — and each points toward different causes, so identifying which one you have is the first fork in the diagnosis.
Diagnose the cause once. Or have it prevented continuously.
Most spam-placement causes are operational and preventable: aligned authentication, managed reputation, clean separated streams, proper warming. EDP runs your sending on dedicated IPs you own, on its own PowerMTA and KumoMTA, with all of it operated as a managed service — so these causes are headed off rather than diagnosed after the fact. Tell us your volume and we'll size it.
Book infrastructure reviewRelated capabilities