You sent the campaign an hour ago. Opens are a third of normal, and a test send to your own Gmail account just landed in spam.
You’ve checked the subject line, re-sent to yourself, and searched your ESP dashboard for a bounce that isn’t there.
The ESP marks the message “delivered” the moment Gmail accepts it; it never tells you which folder it went to, or why.
The next 10 minutes walk through the six reasons Gmail, Outlook and Yahoo file mail as spam, how to tell which one is yours, and the fix for each in the order to try them.
If you’re reading this at 11pm because tomorrow’s send can’t go out like this, you’re in the right place.
Run a free audit → — paste your email headers and see every failing check, with the fix for each. No account.
1. SPF, DKIM or DMARC Is Failing
What it is
SPF, DKIM and DMARC prove that your domain authorized the server that sent the message. When one of them fails or the domains don’t align, Gmail, Outlook and Yahoo treat the email as suspicious — or reject it outright.
- SPF (Sender Policy Framework) — Specifies which IP addresses are allowed to send email from your domain. If you send from a third-party ESP that isn’t listed in your SPF record, every email from that service fails SPF.
- DKIM (DomainKeys Identified Mail) — A cryptographic signature added to your email that proves the message wasn’t altered in transit. Missing or invalid DKIM causes immediate spam scoring increases at Gmail, Yahoo, and Outlook.
- DMARC (Domain-based Message Authentication) — Tells mailbox providers what to do when SPF or DKIM fails (none / quarantine / reject). A missing or misconfigured DMARC record is one of the top reasons emails go to spam today.
How to fix it
1
Run InboxStack’s free DNS Checker — it grades your SPF, DKIM, DMARC, MX, and SSL setup in one scan, no signup.
2
Ensure every sending service (your ESP, CRM, support tool, etc.) is listed in your SPF record with the correct include: mechanism.
3
Configure DKIM with a 2048-bit key minimum. Enable DKIM signing for every sending domain and subdomain.
4
Set DMARC to at least p=quarantine with rua= pointing to a reporting address. Advance to p=reject once your sending infrastructure is verified.
2. Gmail Scores Your Domain or IP Low
What it is
Mailbox providers like Gmail and Yahoo keep a score for every sending domain and IP address. A low score — caused by high spam complaint rates, previous spam activity, or being on a shared IP with a bad sender — causes your emails to be routed to spam or blocked entirely.
How to fix it
1
Check your domain and IP against all major blacklists using InboxStack Brain’s Domain Health. A single blacklist listing can cause near-complete spam routing at affected providers.
2
Open Google Postmaster Tools and look at the domain reputation panel. If it shows “Bad” or “Low,” stop sending immediately and find the cause before resuming.
3
If you’re on a shared IP, consider a dedicated IP. Warm it up properly: start with 200-500 emails/day to your most engaged subscribers and ramp over 4-6 weeks.
4
Submit delisting requests to any blacklist you appear on after you’ve found and fixed the cause. Never submit a delisting request before fixing the underlying issue.
3. No Engagement from Recipients (Spam Trap Hits)
What it is
Gmail, Yahoo, and Outlook all factor recipient engagement into their spam decisions. If large portions of your list never open, click, or interact with your emails, providers interpret this as evidence that recipients don’t want your email — and route future sends to spam. Sending to spam traps (inactive/recycled addresses) drags your domain’s score down far faster.
How to fix it
1
Suppress subscribers who haven’t opened or clicked in 90+ days (6 months for low-frequency senders).
2
Run a re-engagement campaign before suppressing. Segment cold subscribers and send a single “Are you still interested?” email — only keep those who respond.
3
Use double opt-in for new subscribers. It’s the single most effective way to prevent spam traps and invalid addresses from entering your list.
4. Spam Trigger Words and Content Issues
What it is
Content-based spam filters scan your subject line, preheader, and email body for patterns associated with spam. While modern providers rely less on word-matching than they did a decade ago, certain patterns — excessive exclamation marks, misleading subject lines, large image-to-text ratios, suspicious URLs — still increase spam scoring.
How to fix it
1
Avoid deceptive subject lines (e.g., “Re:” or “Fwd:” on cold emails, false urgency). Gmail and Yahoo’s spam filters are specifically trained on deceptive subject patterns.
2
Maintain a healthy text-to-image ratio. Emails that are primarily images with minimal text score poorly with all major providers.
3
Use consistent branding and avoid URL shorteners in your email body. Link to domains that have SPF, DKIM and DMARC in place and a clean history.
5. Sending Too Much, Too Fast (Volume Problems)
What it is
Sudden volume spikes — sending 100,000 emails from a domain that normally sends 1,000 — trigger spam filters at every major provider. This is the leading reason cold email lands in spam for senders who haven’t warmed up their infrastructure.
How to fix it
1
Warm up new sending domains and IPs gradually. Never jump to high volumes on day one.
2
Watch your spam complaint rate in Google Postmaster and Yahoo Postmaster. Keep it below 0.1% at all times (below 0.08% is the target).
3
InboxStack Brain’s alert system watches for spam-rate spikes in real time — it flags a volume jump the moment it starts, before Gmail marks the domain down.
6. Your Domain Is on a Blacklist
What it is
Blacklists (Spamhaus, Barracuda, SORBS, URIBL, and others) maintain lists of domains and IPs known to send spam. Being listed — even on a minor blacklist — can cause significant spam routing at affected providers. Many senders don’t know they’re blacklisted until their inbox rates crash.
How to fix it
1
Run an immediate blacklist check using InboxStack Brain’s Domain Health scan. It checks against all major blacklists simultaneously.
2
Identify the cause of the listing (spam complaint spike, malware in your email, or a compromised sending account) before requesting removal.
3
Submit a delisting request to each blacklist provider after fixing the cause. Spamhaus delisting typically takes 24-48 hours if your case is valid.
How InboxStack Brain Tells You Which One It Is
Every issue above throws off a signal that InboxStack Brain’s alert system catches — spam rate spikes, SPF/DKIM/DMARC failures, blacklist listings, drops in Gmail’s domain score, engagement declines — the moment it appears. The RCA Inspector maps the chain of events and tells you which of the six is responsible for your mail going to spam. The Resolution Plans module writes a fix playbook for your exact situation.
Instead of working through this checklist by hand, you get a system that watches everything and tells you exactly where to focus.
Frequently Asked Questions
Why are my emails going to spam even though I have SPF and DKIM set up?
Passing SPF and DKIM is necessary but not sufficient. Even with both configured, your emails can land in spam because of a low domain score at Gmail, low recipient engagement, a spam complaint spike, missing DMARC alignment, or content issues. For the full diagnostic walkthrough, see: DMARC Passes But Still in Spam — Why This Happens. InboxStack Brain’s Deliverability DNA runs a full audit and names the factor that is sending your mail to spam in your specific case.
Why do my emails go to spam on Gmail but not Outlook?
Gmail and Outlook use different spam algorithms and weight different signals. A divergence between providers (e.g., Gmail spam, Outlook inbox) almost always points to a Gmail-specific problem, often the Google Postmaster domain reputation score or Gmail’s engagement signals. InboxStack Brain’s Radar Monitor detects provider divergence in real time and the RCA Inspector names the provider-specific cause.
My emails suddenly started going to spam — what happened?
Sudden spam routing is almost always caused by: (1) a spam complaint rate spike above 0.1%, (2) a new blacklist listing, (3) a DNS change (e.g., adding a new ESP without updating SPF), or (4) a volume spike on a new or under-warmed sending domain. InboxStack Brain’s alert system detects the signal within minutes of it appearing and opens an incident with the RCA Inspector tracing the exact cause.
How do I stop cold emails from going to spam?
Keeping cold email out of spam requires: properly warmed sending infrastructure, correct SPF/DKIM/DMARC setup on dedicated sending domains, low sending volumes (200-500/day per domain during warmup), personalized content with good text-to-HTML ratios, and a close watch on the complaint rate. InboxStack Brain watches cold-email domains and alerts you the moment any signal shows your emails are being flagged as spam.