Start With the Placement Pattern
“Going to spam” describes an outcome, not one technical fault. Before editing DNS or moving platforms, establish which messages, recipients and providers are affected. A consistent pattern narrows the investigation far more effectively than another generic email score.
| What you observe | Where to investigate first |
|---|---|
| Only Gmail recipients are affected | Google-specific reputation evidence, recipient engagement, complaint signals, authentication results and message patterns. |
| Only Outlook or Microsoft recipients are affected | Microsoft-specific blocks or filtering, IP/domain reputation, bounce responses and sending-infrastructure history. |
| Most providers are affected | Authentication alignment, infrastructure, domain/IP reputation, list quality, complaints and recent sending changes. |
| Only one sending platform is affected | That platform's DKIM, return path, tracking domain, IP arrangement, configuration and audience source. |
| The problem started after a volume spike or migration | Ramp pattern, new IP/domain reputation, changed authentication, recipient mix and differences between old and new infrastructure. |
| Only one recipient or company is affected | Local filtering, allow/block rules, security gateway decisions and the recipient organisation's policies. |
12 Common Reasons Emails Go to Spam
Several causes can exist at the same time. Treat this list as an investigation map, not a sequence of switches to change without evidence.
SPF, DKIM or DMARC does not align
A record can exist yet fail for the actual sending domain, return path or message stream. Alignment matters more than the presence of three DNS entries.
Several platforms share one domain
Business mail, CRM, newsletter and transactional tools can conflict, exceed SPF limits or leave an old sender unauthenticated.
The domain has weak sending history
A new, dormant or previously abused domain gives mailbox providers less positive evidence and can react badly to rapid scale.
The sending IP carries risk
Shared pools can be influenced by other senders, while dedicated IPs require enough responsible volume and active management to build reputation.
The list contains poor-quality recipients
Old, purchased, guessed or weakly consented addresses increase bounces, inactivity, complaints and spam-trap risk.
Recipients mark messages as spam
Authentication cannot offset unwanted mail. Targeting, expectation, frequency and an obvious opt-out path influence complaint behaviour.
Recipients consistently ignore the mail
Low interaction is not a complete diagnosis, but sustained weak engagement can reinforce the view that a mail stream is not wanted.
Sending changed too quickly
Sudden increases, irregular bursts or a new type of campaign can look unlike the domain's established pattern and expose list-quality problems.
Links, identity or content look inconsistent
Mismatched brands, obscured destinations, compromised links, excessive redirects or misleading sender details can reduce trust.
Bounces and opt-outs are not suppressed
Continuing to contact invalid or opted-out recipients generates avoidable negative signals and may create legal or platform-policy risk.
An account or domain was compromised
Unauthorised sending can damage reputation quickly. Investigate account activity, credentials, unexpected DNS changes and unfamiliar campaigns.
A local gateway or rule overrides placement
Corporate security products, personal rules and organisation-specific policies can filter mail even when wider placement is healthy.
Why SPF, DKIM and DMARC May Not Be Enough
Authentication answers important identity questions: which systems may send, whether the signed message is intact and whether identifiers align with the visible From domain. It does not tell a mailbox provider that recipients want the message, that the list is healthy or that the sender has a positive reputation.
A common failure pattern is to keep editing records after all three mechanisms pass. That can introduce new problems without changing the real cause. Confirm the results on an affected message, map every legitimate sender and then move to reputation, platform and recipient evidence.
Provider requirements change. Higher-volume and marketing senders should check the current requirements published by Google's email sender guidelines and Yahoo's sender best practices. Both providers publish their own authentication, complaint-management and unsubscribe expectations.
Use those pages as current requirements for their services—not as a promise that compliance guarantees inbox placement.
A Practical Spam-Placement Diagnostic Checklist
Preserve the original evidence before making changes. A header or bounce response captured now can be more useful than a perfect-looking DNS record after the fact.
- Identify the mail stream. Is this person-to-person business mail, a newsletter, CRM campaign, cold outreach or a transactional message?
- Record the affected providers and timeline. Note when the issue began, which recipient domains are affected and whether it follows a migration, campaign or volume change.
- Capture headers and delivery responses. Keep examples from both inbox and spam placement plus any bounce, deferral or rejection text.
- Check SPF, DKIM and DMARC on the actual message. Confirm pass and alignment results rather than relying only on public DNS lookup tools.
- Map every authorised sender. Include business mail, CRM, support, invoicing, forms, marketing, transactional and automation platforms.
- Review reputation and complaint evidence. Use available provider dashboards, blocklist context and sending-platform data while recognising that no single score is complete.
- Compare list source, engagement and volume. Look for old or purchased data, abrupt growth, weak consent, repeated non-engagement or missing suppression controls.
- Change one justified layer at a time. Record the prior state, implement the highest-confidence correction and define how its effect will be observed.
Fixes That Commonly Make the Problem Worse
Urgency encourages broad changes, but reputation problems are easier to diagnose when the sending environment remains controlled.
- Replacing DNS records without recording the previous configuration.
- Moving providers before proving the current platform is the cause.
- Sending larger campaigns to “test” an already weak reputation.
- Buying or appending more addresses to compensate for low engagement.
- Creating many new domains to avoid repairing the underlying practice.
- Trusting one automated score as a complete deliverability diagnosis.
When the Cause Is Still Unclear
If several platforms send from the domain, providers behave differently or previous authentication changes did not improve placement, a wider investigation is usually more efficient than another isolated fix.
Emails Going to Spam: Frequently Asked Questions
Why are my emails going to spam even with SPF, DKIM and DMARC?
SPF, DKIM and DMARC prove and align sending identity, but they do not guarantee inbox placement. Messages can still be filtered because of sender or IP reputation, complaints, weak engagement, list quality, abrupt volume changes, content and link signals, or conflicts between several platforms sending from the same domain.
Can I tell exactly why Gmail or Outlook put an email in spam?
Mailbox providers do not expose every filtering signal or a complete reason for each placement decision. Headers, authentication results, bounce responses, provider dashboards and controlled tests can narrow the cause, but a reliable diagnosis usually combines several sources rather than claiming certainty from one score.
Will changing email providers stop my emails going to spam?
Not automatically. A migration can help when the current infrastructure is genuinely part of the problem, but domain reputation, audience quality, complaint history and sending behaviour can follow you. Moving without diagnosing the cause can reproduce the same problem on the new platform.
How long does sender-reputation recovery take?
There is no universal recovery period. Timing depends on the cause, severity, mailbox providers involved, sending frequency, audience response and whether harmful activity has stopped. Technical records can be corrected quickly, while reputation changes usually need consistent good signals over time.
Should I use an email warm-up tool?
Do not treat automated warm-up as a universal repair. First identify whether the problem is authentication, infrastructure, reputation, audience or sending practice. Review the policies of your email and mailbox providers before using any service that generates artificial engagement.
Are cold emails always treated as spam?
Not every unsolicited message is placed in a spam folder, but cold outreach carries higher complaint and engagement risk and must comply with applicable law and provider rules. Relevant targeting, honest identity, appropriate volume, easy opt-out and disciplined list practices matter; authentication alone does not make unwanted mail acceptable.
When should I hire an email deliverability consultant?
Specialist help is useful when several platforms send from the domain, different mailbox providers behave differently, performance declined without one clear cause, business-critical mail is affected, or previous record changes did not improve placement. A consultant should explain evidence, priorities and limits rather than promise guaranteed inbox placement.