Emails Going to Spam Despite SPF, DKIM and DMARC: Causes

When SPF, DKIM and DMARC all pass but mail still lands in spam, the cause is usually reputation or recipient behaviour: high complaint or bounce rates, a poor list, a sudden volume jump, a new or burned domain, or content that triggers filters. Authentication proves who you are; it does not prove you are wanted.

First, make sure the pass is real

Before blaming reputation, confirm the “pass” in your dashboard matches reality.

1. Send a real message through the same service you use for production.
2. Read the headers and check spf, dkim and dmarc, and the domain beside each.
3. Confirm alignment: DMARC only passes when SPF or DKIM passes for a domain matching the visible From.

A DNS tool such as BusinessMCP’s free checker grades records, but BusinessMCP’s own page states passing does not guarantee inbox placement and that volume, bounce and complaint rates, list quality and content matter too. If the real headers fail, return to the header-reading walkthrough.

BusinessMCP’s SPF, DKIM and DMARC guide puts the situation briefly: authentication is necessary but not sufficient, and “everything passes but mail still lands in spam” is a known category of its own.

A diagnostic table

Symptom	Most likely cause	How to confirm	Fix
Spam at all providers, new domain	No reputation or no warm-up	Domain age, sending history	Ramp slowly over weeks
Spam started after a big send	Volume spike or complaints	Compare volume and complaints by day	Reduce, send to engaged only
Spam at Gmail only	Gmail reputation or spam rate	Postmaster Tools (if populated)	Lower complaints, clean list
Hard bounces rising	List quality	Bounce log	Verify addresses
Only promotional messages affected	Content or link patterns	Seed test with variants	Simplify content
Cold outreach lands in spam	Cold mail on poor domain	Domain metrics	See cold email deliverability

Cause 1: complaints

A complaint is a recipient pressing “report spam”. Google asks bulk senders to stay under 0.3% user-reported spam and recommends staying under 0.1%. At low volume the arithmetic is harsh: three reports per 1,000 delivered messages is 0.3%. Sources of complaints include unclear opt-in, hard-to-find unsubscribe links and sending more often than promised. One-click unsubscribe headers and a visible link both reduce them; see Gmail and Yahoo requirements.

Key takeaway: the reporting button is the strongest negative vote a recipient has. Making leaving easy keeps people from using it.

Cause 2: bounces and bad lists

Sending to addresses that do not exist, or that belong to spam traps, signals a careless list. BusinessMCP cites about 2% bounces as a benchmark and persistent rates above about 5% as the danger zone. Verify, suppress hard bounces and avoid purchased lists.

Cause 3: no reputation or a damaged one

New domains have no history. Providers treat unknown senders cautiously, which is why gradual ramping matters; BusinessMCP’s guide describes roughly two to four weeks before a new domain carries full volume. A domain that has been damaged by earlier complaints may need retirement. The advice for cold programs is to retire a domain whose metrics stay red after the cause is fixed. Keep outreach off your primary domain, as explained in domain versus subdomain.

Cause 4: sudden changes in pattern

Going from a trickle to a flood, changing sending platform or IP overnight, or suddenly mailing an old list all look like compromise or abuse. Keep volume steady and introduce changes gradually.

Cause 5: content and links

Content is a smaller factor, yet it still counts at the margin:

• Link shorteners and long redirect chains.
• Image-only messages with little text.
• Misleading subject lines or From names.
• A tracking domain with a poor reputation, shared with other senders.
• Missing plain-text alternative.

Test by sending a stripped-down version to seed mailboxes and adding elements back one by one.

Cause 6: shared infrastructure

On shared IP pools, other customers’ behaviour can affect you. If a platform’s shared range is dragging down results and you send enough volume, ask about dedicated IPs. This is a fit question for larger senders, not a default fix, because a dedicated IP with no history needs its own warm-up.

What to do, in order

1. Verify real-message authentication and alignment.
2. Check bounce rate and suppress every hard bounce.
3. Check complaints and unsubscribe flow.
4. Review recent volume and pattern changes.
5. Reduce volume to your most engaged recipients for a couple of weeks.
6. Resume gradually and watch the numbers.

For a broader plan, see how to improve email deliverability.

When to get help

If a major provider blocks your mail outright, the bounce text usually links to a postmaster page with a mitigation form. Follow it, and be ready to describe the cause and the fix. Google’s guide for admins on preventing spam placement is a primary reference. BusinessMCP’s cold email deliverability and compliance guide adds outbound-specific advice. No external party can promise recovery on a timetable; consistent, wanted sending is what rebuilds trust.

Reading spam-classification headers

Some providers add headers explaining their verdict. Gmail’s “Show original” view displays authentication results; other providers may add headers such as an X-Spam-Status or similar score line, with names that vary by system. When you find one, note any reason codes or scores and compare them across messages that did and did not reach the inbox. The aim is not to decode a proprietary system exactly, but to spot what differs between a good and a bad send: a different link domain, a changed From name, a new sending IP.

An example investigation

Suppose a company’s monthly newsletter has reached the inbox for a year, then suddenly lands in spam at one provider. The authentication headers still pass. The investigation might run like this:

1. Compare complaint and bounce counts for the last three sends. Complaints doubled after a campaign that went to a long-dormant segment.
2. Check the list source for that segment. It was imported from an old CRM with no recent engagement.
3. Pause sending to that segment, mail only recent openers or clickers for two weeks, and keep the cadence steady.
4. Watch whether placement recovers. If it does, the cause was list quality, and the fix is a sunset policy.

Nothing in that chain involved DNS. That is typical, and it is why the free BusinessMCP checker is a first step rather than the whole answer.

Related reading on the sender side

Because the same causes keep appearing, BusinessMCP’s guides are a handy second source. Its cold email infrastructure guide covers domain separation, warm-up and volume limits, and its SPF, DKIM and DMARC guide covers the “everything passes but mail still lands in spam” case. They are vendor documents, so compare their numbers with the provider pages before relying on them.

When the problem is not you

Occasionally the cause is on the receiving side: a provider incident, a regional filtering change or a recipient’s own rules. If only one recipient or one company sees the problem, ask them to check their quarantine and allow-list settings and share the headers of a message that landed in spam. A short human conversation often resolves what no tool can.