Why Is My Cold Email Going to Spam? How to Diagnose and Fix It
By Moe Ameen, founder of BILT · Published · Updated
Cold email goes to spam when it fails a mailbox provider's rules or when recipients mark it as spam. Diagnose in this order: read the bounce code (Gmail's 4.7.x and 5.7.x codes name the failed requirement), check that SPF, DKIM and DMARC pass in the message headers, then check Google Postmaster Tools for a spam rate at or above 0.3%. Rewrite copy only after those three are clean.
Key takeaways
- Gmail rejection codes tell you which sender requirement failed. Read them before changing anything.
- Open a delivered message and check the header for spf=pass, dkim=pass and dmarc=pass.
- A Postmaster Tools spam rate at 0.3% or higher breaks Google's and Yahoo's limits; Google recommends staying under 0.1%.
- Fake "Re:" subjects, purchased lists and unreadable links are named in Google's guidelines as things to avoid.
When cold email starts landing in spam, the instinct is to rewrite the email. That's usually the last thing to try.
Gmail and Yahoo publish their rules, and Gmail tells you in the bounce which one you broke. Start with the evidence the providers give you.
What does the bounce message tell you?
A Gmail rejection includes a status code and a reason, and the code family tells you whether the failure is temporary or a block.
Google's sender FAQ says temporary failures come back as 4.7.x and blocked messages as 5.7.x, each naming the specific requirement that failed. Pull five or ten recent bounces from your sending tool and read the text. If it mentions authentication, you have a DNS problem. If it mentions rate or reputation, you have a volume or complaint problem. Those need different fixes.
How do you check SPF, DKIM and DMARC on a sent message?
Send a cold email to your own Gmail address, open it, choose "Show original", and look for spf=pass, dkim=pass and dmarc=pass.
Any fail or none is your first fix. For bulk senders, Google also requires the From domain to align with the SPF or DKIM domain, so a message can pass SPF on your provider's domain and still fail alignment. Yahoo requires bulk senders to publish DMARC at p=none or stricter, and the DMARC check has to pass.
What spam rate triggers filtering?
Google and Yahoo both set the limit at a 0.3% user-reported spam rate, and Google recommends staying below 0.1%.
Google measures this in Postmaster Tools, which you can set up for any domain you own. A worked example with illustrative numbers: 2,000 cold emails delivered to Gmail in a day with 8 "report spam" clicks is a 0.4% rate, over the limit. The fix there is fewer, better-matched recipients. New subject lines won't move it.
| Symptom | Likely cause | Where to check | Fix |
|---|---|---|---|
| 5.7.x bounces citing authentication | Missing SPF/DKIM or failed DMARC | Bounce text; message headers | Correct the DNS record named in the bounce |
| 4.7.x temporary failures | Volume jump or reputation dip | Bounce text; send volume by day | Cut daily volume and raise it slowly |
| Delivered but in spam everywhere | Complaints or a cold new domain | Postmaster Tools spam rate | Smaller, better-matched list; slower ramp |
| Spam at Gmail only | Alignment failure or Gmail-specific complaints | dmarc= result in Gmail headers | Align From with SPF or DKIM domain |
| High bounce on new list | Stale or bought addresses | Hard-bounce count per list | Verify addresses before sending; drop bought lists |
Symptom, likely cause and where to check
Can the email content itself cause spam placement?
Yes, but Google's guidelines point to a few specific practices rather than lists of "spam words."
Google says not to start a subject with "Re:" or "Fwd:" unless the message is a real reply or forward, and to keep links in the body visible and easy to understand. The FTC adds a legal layer: under CAN-SPAM, the subject line must accurately reflect the content. A fake reply thread breaks both. Image-only emails and heavy tracking links aren't named in Google's rules, so treat advice about them as experience, not policy.
Should you fix the domain or replace it?
Fix the domain if the cause was a DNS mistake; consider replacing it if complaints were high for weeks.
An authentication error stops hurting as soon as the record is correct. A reputation built on weeks of complaints takes longer to recover, and since cold outreach domains exist to be expendable, retiring one is often faster. Before you send from the replacement, fix whatever list or volume problem burned the first one.
Who is this for, and who should skip it?
Best for
- Senders seeing spam placement or bounces on an existing cold program
- Anyone who wants to fix deliverability from evidence instead of guesswork
Not ideal for
- Brand-new setups; start with domain and warm-up setup first
- Mail to opted-in subscribers, where list-unsubscribe and engagement rules differ
What else do people ask?
Will changing my subject line get me out of spam?
Only if the subject was misleading, such as a fake "Re:". Most spam placement traces to authentication, volume or complaints, which a new subject line won't fix.
How do I see my Gmail spam rate?
Verify your sending domain in Google Postmaster Tools. It reports the user-reported spam rate that Google measures against the 0.3% limit.
Why does mail reach Outlook but not Gmail?
Gmail requires DMARC alignment for bulk senders, so a message that passes SPF on your provider's domain can still fail at Gmail. Check the dmarc= result in Gmail's message headers.
Does Yahoo follow the same rules as Gmail?
Mostly. Yahoo's bulk sender rules also require SPF, DKIM, a passing DMARC policy, one-click unsubscribe and a spam rate under 0.3%.
The takeaway
Diagnose spam placement from the evidence Gmail and Yahoo hand you: bounce codes, header authentication results and the Postmaster Tools spam rate. Fix DNS errors immediately, cut volume and tighten the list for complaint problems, and leave copywriting for last.
How do we know this?
We read Google's sender guidelines and FAQ, Yahoo's sender best practices and the FTC's CAN-SPAM guide on November 4, 2026. The spam-rate example uses illustrative numbers.
Sources
- Google Workspace Admin Help: Email sender guidelines (accessed November 4, 2026)
- Google Workspace Admin Help: Email sender guidelines FAQ (accessed November 4, 2026)
- Yahoo Sender Hub: Sender best practices (accessed November 4, 2026)
- FTC: CAN-SPAM Act: A Compliance Guide for Business (accessed November 4, 2026)