If you are asking "why are my emails going to spam", the short answer is that a mailbox provider decided your message looked risky, and it almost always decided that for one of five reasons: your mail failed authentication, your domain or IP has a poor reputation, your list contains people who never wanted the mail, your content or formatting tripped a filter, or your sending pattern changed suddenly. The fix depends on which one it is, so guessing (rewriting subject lines, swapping words like "free") wastes days.
This guide gives you a diagnostic order to follow, 15 concrete causes with a "how to confirm" and "how to fix" for each, a triage table, a short lesson on reading message headers, and a recovery plan for after a reputation hit.
Key takeaways
- Diagnose in order: one provider or all of them, then authentication, reputation, list quality, content and finally sending pattern. Most problems are found in the first three steps.
- Headers don't lie: the
Authentication-Resultsheader in any spam-foldered message tells you in ten seconds whether SPF, DKIM and DMARC passed. - Complaints drive placement: Google asks senders to keep the user-reported spam rate below 0.10% and never reach 0.30%. List quality fixes more spam problems than copy edits do.
- Bulk rules are now enforced: Gmail, Yahoo and Microsoft reject or junk non-compliant bulk mail, so authentication and one-click unsubscribe are table stakes.
- Recovery is slow but predictable: fix the cause, cut volume to your most engaged contacts, then ramp back up over weeks while watching complaint and bounce rates daily.
Why are my emails going to spam? Start with this diagnostic order
Filters at Gmail, Outlook.com and Yahoo weigh hundreds of signals, but you only need to check them in a sensible order. Each step below either finds the cause or rules out a whole group of causes, so do not skip ahead to content.
- Is it every mailbox provider or just one? Send the same campaign to test addresses at Gmail, Outlook.com (or Hotmail), Yahoo and a company Microsoft 365 or Google Workspace mailbox. If only Outlook junks you, read our guide to emails going to junk in Outlook, because Microsoft's filtering and tools are different. If Gmail places you in Promotions rather than Spam, that is a tab, not a filter verdict: see how the Gmail Promotions tab works. If every provider spam-folders you, the cause is almost always authentication or reputation.
- Authentication. Open a delivered test message, view the original source and read the
Authentication-Resultsheader (example below). Anyfail,softfail,noneorpermerrorfor SPF, DKIM or DMARC is your first fix. - Reputation. Check Google Postmaster Tools for spam rate, Microsoft SNDS for IP data, and the major blocklists. Recent bounces with codes such as
421 4.7.0or550 5.7.1that mention "reputation" confirm it. - List quality. Look at bounce rate, complaint rate and the age of the segment you mailed. Old, purchased or never-confirmed addresses are the usual trigger for a sudden drop.
- Content and format. Only now look at links, images, HTML and headers such as
List-Unsubscribe. - Sending pattern. Compare volume, frequency, sending domain and provider with the weeks before the problem started. A jump in volume or a new domain often explains everything else.
Quick triage table: symptom to likely cause
Use this table when you need a first guess in under a minute. Then confirm with the matching cause below before you change anything.
| What you see | Most likely cause | Check first |
|---|---|---|
| Everything goes to spam at every provider, including test sends | Authentication failure or blocklisted domain/IP | Authentication-Results header, blocklist lookup (causes 1–4, 7) |
| Spam only at Gmail | High user-reported spam rate or poor Gmail domain reputation | Postmaster Tools spam rate and compliance status (causes 5, 9) |
| Junk only at Outlook.com/Hotmail | Microsoft IP reputation, missing DMARC for high volume | SNDS data, bounce text with 5.7.515 (causes 3, 6) |
| Inbox for small tests, spam for the full campaign | List quality: unengaged or old segment, spam traps | Segment age and bounce rate (causes 10–12) |
| Problem started right after switching provider or domain | No warm-up, missing DKIM on new domain, new shared IP | Volume history and DKIM d= domain (causes 2, 6, 8) |
| Only one campaign landed in spam | Content or link problem, or a burst of complaints | Links in that email, complaint count for that send (causes 9, 13) |
Bounces with 421 4.7.x deferrals at Gmail | Rate limiting for failed requirements or unusual volume | The exact code and text in your provider's bounce log (causes 1–4, 15) |
| Open rates fell gradually over months | Mailing too many inactive contacts | Engagement by segment (cause 12) |
If open rates dropped but you are not sure whether it is placement or tracking, read why your email open rate dropped before you assume a spam problem; privacy features inflate and distort opens.
How to read message headers (Authentication-Results)
Every receiving server records its verdict on your authentication in a header called Authentication-Results. Reading it takes ten seconds and replaces most guesswork.
Where to find the raw headers
- Gmail (web): open the message, click the three-dot menu next to Reply, choose Show original. Gmail also shows a summary box with SPF, DKIM and DMARC as PASS or FAIL.
- Outlook.com: open the message, click the three-dot menu, then View and View message source.
- Outlook desktop (Windows): open the message, then File, Properties, and read the Internet headers box.
- Yahoo Mail: open the message, click the three-dot menu, choose View raw message.
A passing result and a failing one
dkim=pass header.i=@example.com header.s=s1 header.b=Ab12Cd34;
spf=pass (google.com: domain of bounce@mail.example.com designates 203.0.113.25 as permitted sender) smtp.mailfrom=bounce@mail.example.com;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=example.com
Authentication-Results: mx.google.com;
dkim=pass header.i=@esp-shared.net header.s=k1 header.b=Zx98Yw76;
spf=pass (google.com: domain of bounces@esp-shared.net designates 198.51.100.7 as permitted sender) smtp.mailfrom=bounces@esp-shared.net;
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=example.com
In the first block, DKIM is signed by example.com, SPF passes for mail.example.com and DMARC passes because both share the organizational domain shown in header.from. In the second, SPF and DKIM both "pass", but for the provider's domain, not yours. Nothing aligns with example.com, so DMARC fails. It is one of the most common misconfigurations after someone connects a new sending provider.
What each field tells you
header.iorheader.d: the domain that signed DKIM. It should be your domain or a subdomain of it.smtp.mailfrom: the envelope sender (Return-Path) that SPF checked. For alignment it should be your domain or subdomain.header.from: the visible From domain that DMARC protects.dis=: what the receiver did because of your DMARC policy (NONE,QUARANTINE,REJECT).
Also scan the Received lines for ESMTPS or a TLS version, which shows the message travelled over an encrypted connection.
Authentication causes (1–4)
These are binary: either they pass or they do not. Fix them first, because no amount of good content compensates for failed authentication at Gmail, Yahoo or Outlook.com. Setup is covered step by step in our SPF, DKIM and DMARC setup guide; below is only how to spot each failure.
1. SPF is missing, broken or over the lookup limit
How to confirm: the header shows spf=fail, softfail, none or permerror. Run dig +short TXT yourdomain.com and check there is exactly one record starting with v=spf1. More than ten DNS-querying mechanisms (each include:, a, mx, redirect) causes permerror, and two SPF records on one domain is also an error.
How to fix: merge into one record, remove providers you no longer use, and point your provider's custom MAIL FROM (Return-Path) at a subdomain so its SPF include lives there instead of on your root domain.
2. DKIM is missing or signed with your provider's domain
How to confirm: dkim=none, dkim=fail, or dkim=pass with a header.i that is not your domain. A body hash did not verify result means something modified the message after signing (a footer added by a gateway, for example).
How to fix: publish the DKIM records your sending provider gives you for your own domain (Amazon SES Easy DKIM, SendGrid domain authentication and Mailgun domain verification all work this way) and confirm the provider shows the domain as verified. Use a 2048-bit key where supported; Google's email sender guidelines require at least 1024 bits.
3. DMARC is missing or fails alignment
How to confirm: dmarc=fail or no DMARC result at all, or a bounce from Outlook.com reading 550 5.7.515 Access denied, sending domain ... does not meet the required authentication level. Check the record with dig +short TXT _dmarc.yourdomain.com.
How to fix: publish at least v=DMARC1; p=none; rua=mailto:... and make sure DKIM or SPF aligns with the From domain (ideally both). Then read the aggregate reports to find senders you forgot; our guide on how to read DMARC reports walks through the XML. One special case: if your From address is @gmail.com, @yahoo.com or @outlook.com and you send through a marketing platform, DMARC will fail by design. Use your own domain. Google lists "don't impersonate Gmail From: headers" as a requirement for all senders. Once DMARC passes and you move to enforcement, you also become eligible for a logo in the inbox via BIMI.
4. Missing PTR record or no TLS (self-hosted and SMTP relays)
How to confirm: this mostly affects people running their own mail server or a VPS relay. Run dig +short -x 203.0.113.25 (your sending IP); it should return a hostname, and that hostname should resolve back to the same IP. Gmail's deferral 451 4.7.23 or rejection 550 5.7.25 names the missing PTR, and 421 4.7.29 names missing TLS.
How to fix: ask your hosting provider to set reverse DNS to a hostname on your domain, add a matching A record, and enable STARTTLS on the server. Managed providers such as Amazon SES handle both for you, which is one reason most marketers should not run their own MTA.
Reputation causes (5–8)
Reputation is the memory mailbox providers keep of your domain, IPs and even the URLs in your messages. It is built from complaints, engagement, bounces and trap hits over weeks. For how it is scored and tracked, see our deep dive on email sender reputation.
5. Your sending domain has a poor reputation
How to confirm: authentication passes, but Gmail still spam-folders you, and bounces mention "very low reputation of the sending domain" (421 4.7.0). In Google Postmaster Tools, check the spam rate and compliance status dashboards for your domain. Google is retiring the legacy Domain and IP reputation dashboards in the newer Postmaster Tools, so lean on spam rate and compliance data.
How to fix: there is no switch. Stop mailing low-engagement segments, fix complaint sources, and follow the recovery plan below. Do not jump to a fresh domain: providers link domains through shared infrastructure and content, and a new domain without history starts at a disadvantage anyway.
6. Shared IP neighbors or a cold dedicated IP
How to confirm: you are on a shared pool and problems appeared without any change on your side, or bounces cite "very low reputation of the sending IP address". For Microsoft, register your IPs in SNDS (Smart Network Data Services) to see filter results and complaint data, if you have a dedicated IP.
How to fix: on a shared pool, contact your provider with the bounce text; they can move you. If you send enough volume for a dedicated IP, it isolates you from neighbors but you inherit full responsibility, and it must be warmed up first.
7. Your IP or domain is on a blocklist
How to confirm: bounces quote a list name (Spamhaus, Barracuda, SpamCop) or a lookup tool shows your IP, sending domain or a domain linked in your emails. Our email blacklist check guide covers which lists matter and which are noise.
How to fix: find and fix the cause before requesting removal (usually a spam trap hit or an old segment), then use the list's delisting form. Spamhaus offers a free lookup and removal process at check.spamhaus.org. If a link domain is listed (a shared URL shortener, for instance), remove it from your template.
8. New domain or IP with no warm-up, or a sudden volume spike
How to confirm: the problem began with a new domain, a new provider, a new dedicated IP or your first large send in months. Gmail's 421 4.7.28 ("unusual rate of email") is the classic signal.
How to fix: drop back to a volume that delivers, send to your most engaged contacts first and increase gradually. Schedules by list size are in our IP and domain warm-up guide.
List quality causes (9–12)
When authentication passes and you are not blocklisted, the list itself is usually the problem. Filters learn from what recipients do with your mail, so the people on your list largely decide your placement.
9. Too many people mark your email as spam
How to confirm: Google Postmaster Tools shows the user-reported spam rate per day. Google's guidelines ask senders to keep it below 0.10% and avoid ever reaching 0.30%, and its sender guidelines FAQ says bulk senders above 0.3% lose eligibility for mitigation until they stay below it for 7 consecutive days. Yahoo's complaint feedback loop and Microsoft's JMRP give per-message complaint data.
How to fix: find which segment, source or campaign produces complaints, make the unsubscribe link obvious, set expectations at signup, and reduce frequency for people who rarely engage. The full playbook is in our article on spam complaint rate.
10. High bounce rate from old or unverified addresses
How to confirm: hard bounces (550 5.1.1 user unknown) that climb from one campaign to the next are a warning sign, and sending providers such as Amazon SES monitor account bounce rates and can pause sending when they get too high. Check your provider's bounce reports by campaign and by list source.
How to fix: suppress every hard bounce permanently, verify lists older than a few months before mailing, and never import a list you did not collect yourself. See email bounce rate for benchmarks and handling rules.
11. Spam traps on your list
How to confirm: sudden blocklist listings, especially on Spamhaus, after mailing an old segment or a purchased, scraped or co-registration list. You will never see which address is a trap.
How to fix: stop mailing the segment that preceded the listing, re-confirm or remove contacts with no engagement in a long time, and use confirmed opt-in for risky signup sources. Our guide to spam traps explains pristine, recycled and typo traps.
12. Mailing contacts who stopped engaging
How to confirm: placement is fine for recent signups but poor for the full list; a large share of your list has not opened or clicked in six months or more.
How to fix: segment by last engagement, send a re-engagement series to the inactive group and sunset those who do not respond. Step-by-step rules are in how to clean your email list.
Content and format causes (13–14)
Content matters less than most people think, but it is the deciding factor once everything else is clean. Our guide to AI email copywriting and spam scores covers wording; here we focus on the technical patterns filters actually punish.
13. Links, images and HTML that look like spam
How to confirm: one campaign underperforms while others land fine. Look for public URL shorteners, links whose visible text shows a different domain than the actual href, image-only emails with little text, attachments in marketing mail, and HTML pasted from a word processor. Gmail's 421 4.7.0 "suspicious due to the nature of the content or the links within" confirms it.
How to fix: link to your own domain (or a branded tracking domain), keep a real text body, send a plain-text alternative, and remove attachments. Run a spam-score check before sending; eMailBase includes one before each send, and free tools such as mail-tester give a similar read.
14. Missing unsubscribe headers or broken message formatting
How to confirm: in the raw message, look for List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click. Also check for duplicate From or Date headers, a missing Message-ID, or malformed encoding of the subject line. Gmail requires bulk senders to support one-click unsubscribe and all senders to format messages according to RFC 5322.
How to fix: make sure your platform or provider adds both headers and that the endpoint actually unsubscribes on a POST request. Implementation details are in one-click unsubscribe. Recipients who cannot find the exit press "Report spam" instead, which feeds cause 9.
Sending pattern cause (15)
15. Erratic volume, changing identities and mixed mail streams
How to confirm: compare your last three months: did you go from monthly to daily, send a 10x campaign for a launch, change the From domain or name, or start sending receipts and newsletters from the same address? Inconsistent patterns look like a compromised account.
How to fix: keep a steady cadence, keep the From identity stable, and separate streams: for example, transactional mail on mail.example.com and marketing on news.example.com, each with its own DKIM and Return-Path. That way a marketing complaint spike does not take your password resets down with it. If you use multiple providers, route each stream consistently instead of randomly spreading one campaign across them; we explain how in multi-server email routing.
Are the 2024 bulk sender rules the reason?
Since February 2024, Gmail and Yahoo have required senders of large volumes to authenticate with SPF and DKIM, publish DMARC, support one-click unsubscribe and keep complaints low. Google's FAQ states that starting November 2025, Gmail is ramping up enforcement on non-compliant traffic with temporary and permanent rejections, and Microsoft added similar authentication requirements for Outlook.com consumer domains in May 2025.
If your bounces show codes like 421 4.7.30 (DKIM did not pass), 421 4.7.32 (From not aligned) or 550 5.7.515 (Outlook.com), the answer to "why are my emails going to spam or bouncing" is compliance. Our full checklist of Gmail, Yahoo and Microsoft bulk sender requirements lists every item and how to test it.
Recovery plan after a reputation hit
Once you have found and fixed the cause, reputation recovers through consistent, low-complaint sending. Expect weeks, not days. This is the sequence we recommend.
- Day 0: stop the bleeding. Pause all sends to old, imported or unengaged segments. Keep transactional mail flowing on its own stream.
- Day 0–2: fix the root cause. Authentication, blocklist delisting, suppressing bounces and complainers, adding one-click unsubscribe. Verify with a test send and the headers.
- Days 3–14: mail only your best contacts. Send to people who opened or clicked recently, at modest volume and steady times. Good engagement from them is what rebuilds trust.
- Weeks 2–6: widen gradually. Add older engaged segments in steps, roughly following a warm-up curve. If complaints or bounces rise after a step, go back one step.
- Daily monitoring. Track spam rate in Postmaster Tools, bounces and complaints per campaign, and seed-list placement. Write down each change so you can tie results to it.
- Escalate only when clean. Microsoft and Yahoo offer sender support forms; Google offers mitigation only to senders who meet all requirements and have kept the spam rate below 0.3%. Requests from senders who have not fixed the cause are usually declined.
Do not burn the domain
Switching to a new domain to "escape" a bad reputation rarely works. The new domain has no history, your content and links are the same, and recipients who complained will complain again. Fix the list and the practices, and the existing domain recovers.
Tooling helps you keep this discipline. eMailBase checks your SPF, DKIM and DMARC records, includes warm-up strategies, and lets you route marketing and transactional mail through separate sending servers, while delivery itself runs through your own Amazon SES, SendGrid, Mailgun or SMTP account.
Frequently asked questions
Why are my emails going to spam when SPF, DKIM and DMARC all pass?
Authentication proves who sent the message, not that recipients want it. If all three pass, look at reputation and list quality next: complaint rate, bounce rate, inactive contacts and blocklists. Also confirm that DKIM and SPF pass for your own domain, not only for your provider's.
Why do my emails go to spam for one person but not others?
Mailbox filters personalize. A recipient who previously deleted your mail unread, or who has a filter rule, can see spam while others see the inbox. Ask them to mark the message as "Not spam" and add you to contacts; if many recipients at one company report it, check that company's security gateway quarantine.
Can a single word in the subject line send my email to spam?
Rarely on its own. Modern filters weigh reputation and engagement far more than individual words. Aggressive formatting (all caps, many exclamation marks, misleading "Re:" subjects) can tip a borderline message, but if you are consistently in spam the cause is almost always elsewhere.
How long does it take to get out of the spam folder?
If the cause was a broken DNS record, placement usually improves within days of the fix. Reputation damage from complaints or spam traps typically takes several weeks of clean, engaged sending to repair, and Google's mitigation eligibility requires at least 7 consecutive days below a 0.3% spam rate.
Does using a free Gmail address as the sender hurt deliverability?
Yes, when you send through any platform other than Gmail itself. The message fails DMARC for gmail.com, and Google's guidelines tell senders not to impersonate Gmail From headers. Send from an address on a domain you own and authenticate.
Spam placement is a symptom, and the cause is usually findable in an hour if you work in order: one provider or all, authentication, reputation, list, content, pattern. Read the headers before rewriting copy, fix the list before buying tools, and recover with patient, engaged sending rather than a new domain.


