Why your cold emails go to spam
Missing authentication records, no warmup on a new sending domain, and a spam complaint rate above the platform's threshold are the most common causes. They usually show up together, not one at a time.
The short answer
- Missing or misconfigured SPF, DKIM or DMARC records are among the most common technical causes of spam placement. Google's guidance requires all three for bulk senders (5,000+ messages a day). Smaller senders benefit from them too.
- Sending at full volume from a new, unwarmed domain or mailbox is a common cause on its own. Mailbox providers weigh a new sender's lack of history against it until a track record builds.
- Google's bulk sender guidelines set a 0.3% spam complaint rate as the hard enforcement line, with 0.10% as the recommended target. Exceeding it means holding below 0.3% for seven consecutive days before eligibility is restored.
- Spam placement usually results from more than one of these at once. Fixing only authentication, or only list quality, often does not resolve the problem on its own.
Why the causes tend to compound rather than act alone
Email landing in spam is rarely explained by one clean cause. It is usually several factors reinforcing each other. Missing or incomplete SPF, DKIM and DMARC records make a mailbox provider less confident the sender is who it claims to be. That alone can push borderline messages to spam. A new domain or mailbox sending at full volume without a warmup period compounds it. The provider has no sending history to weigh in the sender's favor, so it is cautious by default.
List quality adds a third layer: a high bounce rate from stale or invalid addresses, or a spam complaint rate creeping toward Google's stated 0.3% enforcement threshold. Google's guidance (support.google.com, checked September 2026) is explicit that the rate is tracked cumulatively. Exceeding it requires holding below 0.3% for seven consecutive days before restrictions ease. A bad batch's effects linger well past the send that caused them.
Because these factors interact, a sender who fixes authentication but keeps sending an unverified list at full volume from an unwarmed domain often sees only partial improvement. The remaining causes are still working against deliverability.
Common causes and how to check for each
| Cause | How to check |
|---|---|
| Missing or misconfigured SPF/DKIM/DMARC | Check DNS records against the sending domain; tools exist to verify all three |
| No warmup on a new domain or mailbox | Check whether volume ramped gradually or started at full target rate immediately |
| Spam complaint rate near or above 0.3% | Check Google Postmaster Tools or equivalent reporting for the sending domain |
| High bounce rate from an unverified list | Check whether the list was verified before the send, and the actual bounce percentage |
Google's spam complaint thresholds sourced from support.google.com, checked September 2026.
What to actually do to diagnose and fix it
Check all four common causes together. Do not fix one and assume the problem is solved. Confirm SPF, DKIM and DMARC are correctly configured for the sending domain. Confirm the domain or mailbox went through a warmup period before reaching current volume. Check the real spam complaint and bounce rates in available reporting. Verify the list was checked before the send that triggered the problem. Fixing all four together is far more likely to restore deliverability than fixing any one alone.
Disclosure: SalesCrew is our product. Its sender pool applies per-mailbox and per-domain daily caps and enforces suppression at send time. Both reduce the volume and list-quality causes above. It does not configure DNS records or run domain warmup automatically. Those steps happen outside the product, before a mailbox is added to the pool.
A quick fix to one cause does not guarantee immediate recovery
Questions
- Is a single spam complaint enough to hurt deliverability?
- Not by itself. Complaint rate is tracked cumulatively. Google's own guidelines put the hard enforcement line at a 0.3% spam complaint rate. A pattern across a batch matters far more than any single complaint.
- Can correct SPF/DKIM/DMARC setup alone fix a spam problem?
- It removes one common cause, but rarely the only one. Authentication issues, list quality problems, and volume or warmup issues each push email to spam on their own. Fixing one while the others remain often does not restore deliverability.
- How long does it take to recover a domain's reputation after a spam problem?
- It varies. Google's guidance says that recovering from exceeding the spam complaint threshold requires holding below 0.3% for seven consecutive days before eligibility is restored. Broader reputation recovery can take longer, depending on how severe and how long the underlying issue was.