
If you are asking "why are my emails going to spam", the answer is almost always one of seven causes: missing or broken authentication, no DMARC alignment, a spam complaint rate above 0.3%, a damaged sender reputation, a blocklisted IP or domain, a sudden jump in volume, or content and links that filters distrust. Each one can be tested, and most can be fixed in days.
"Delivered" in your email platform only means the receiving server accepted the message. Where it was placed, inbox or spam, is decided after that, and the platform never sees it. This guide works through the seven causes in the order we check them on a client domain.
Why are my emails going to spam when they say delivered?
Your emails say delivered because the receiving server answered with a 250 OK, which is acceptance and nothing more. The filtering decision happens after acceptance, inside Gmail, Outlook or Yahoo, and no bounce is sent when a message is filed as spam.
That is why a campaign can report 99% delivered while replies and opens collapse. The only outside signals are indirect: open rates falling by half or more within a week, replies stopping, or a seed test showing the spam folder.
Mailbox providers weigh three things, in this order:
| Layer | Question the receiver asks | Where you can see it |
|---|---|---|
| Authentication | Is this really from the domain in the From line? | Public DNS and message headers |
| Reputation | How have people treated mail from this domain and IP before? | Google Postmaster Tools, Microsoft SNDS, blocklists |
| Content and behavior | Does this message look and act like wanted mail? | Headers, links, volume pattern |
Authentication comes first because it is pass or fail, and it takes minutes to check. Start there.
What are the 7 causes, and how do you test each one?
The seven causes below cover nearly every case we see. Test them in this order, because each later cause is harder to measure than the one before it.
1. SPF, DKIM or DMARC is missing or broken
Authentication is the most common cause and the fastest to confirm. SPF lists the servers allowed to send for your domain. DKIM signs each message with a key published in DNS. DMARC tells receivers what to do when both fail.
As of November 15, 2026, Google's email sender guidelines require every sender to pass SPF or DKIM, and require senders of 5,000 or more messages a day to pass both and publish DMARC. Microsoft applies the same rule to Outlook.com, Hotmail and Live addresses and rejects mail that fails it with this error:
550 5.7.515 Access denied, sending domain example.com does not meet the required authentication level.
Test it with the SPF record checker, the DKIM checker and the DMARC checker, or read all three at once with the free email deliverability test. The fault we find most is an SPF record that needs more than 10 DNS lookups, which fails for every message even though the record looks correct.
2. Authentication passes, but for the wrong domain
A message can pass SPF and DKIM and still fail DMARC. This happens when your sending platform authenticates with its own domain and not with the domain in your From line. The match between the two is called alignment.
Open a message you sent, view the original, and read the Authentication-Results header:
Authentication-Results: mx.google.com;
dkim=pass header.i=@sendingplatform.example header.s=s1;
spf=pass smtp.mailfrom=bounces.sendingplatform.example;
dmarc=fail (p=NONE) header.from=example.com
Both checks pass, and DMARC still fails, because neither passing domain is example.com. The fix is to set up custom domain signing in the platform, so DKIM signs as your own domain.
3. Your spam complaint rate is too high
A complaint is a person clicking "Report spam". Google tells senders to keep the rate below 0.10% and to avoid ever reaching 0.30%. At 0.30%, that is 3 complaints for every 1,000 messages delivered to Gmail inboxes.
You can only see this number in Google Postmaster Tools, which is free and needs a DNS record to verify your domain. A high rate nearly always comes from mailing people who did not ask for it, or from an unsubscribe link that is hard to find.
4. Your domain or IP reputation is damaged
Reputation is the receiver's memory of your past sending. It falls when recipients delete without reading, complain, or when you hit addresses that no longer exist. We treat a hard bounce rate above 2% on a send as a warning sign that the list is old.
Reputation attaches to both the domain and the sending IP. On a shared IP, another sender's behavior can drag yours down, which is one reason volume senders move to a dedicated IP.
5. You are on a blocklist
A blocklist is a public list of IPs or domains seen sending spam. Receivers consult them at connection time. A listing on Spamhaus affects delivery widely, while many small lists affect almost nothing.
Bounce messages name the list when one is the cause. Look for text like this in your bounce log:
554 5.7.1 Service unavailable; Client host [203.0.113.25] blocked using zen.spamhaus.org
Removal requests work only after the cause is fixed. Asking for delisting first, and being relisted a week later, makes the next request harder.
6. Volume jumped too fast
Receivers distrust sudden change. A new domain or IP that sends 20,000 messages on its first day looks like a spammer who just registered it. So does an established domain that triples its volume overnight.
New sending infrastructure needs a warm-up: a schedule that starts small and roughly doubles every few days while complaint and bounce rates stay low. A typical schedule for a new IP runs 2 to 6 weeks.
7. Content, links and missing unsubscribe headers
Content matters least of the seven, and it is where most people look first. It does count in three specific ways:
- Links to domains with poor reputation. A link shortener or a tracking domain shared with spammers can sink an otherwise clean message.
- No one-click unsubscribe. Google requires bulk marketing mail to carry the
List-UnsubscribeandList-Unsubscribe-Postheaders. - A mismatch between the visible link text and the real URL. Filters treat it as a phishing signal.
"Spam trigger words" are mostly a myth today. A message from a trusted sender can say "free" in the subject and land in the inbox.
How do you tell which cause applies to you?
Match the symptom to the cause. The pattern of the failure usually points to one or two of the seven before any tool is opened.
| What you see | Most likely cause | Check first |
|---|---|---|
| Spam at Gmail and Outlook from day one | 1 or 2 | DNS records and the Authentication-Results header |
| Rejections with a 550 5.7.x code | 1 or 5 | The bounce text itself |
| Inbox for months, then a sudden drop | 3, 4 or 6 | Postmaster Tools spam rate, recent volume |
| Spam at one provider only | 4 | That provider's own reputation tool |
| Cold outreach lands in spam, newsletters do not | 3, 4 or 6 | Complaint rate and sending pattern per mailbox |
| Only messages with a certain link go to spam | 7 | The link's domain |
How do we diagnose it on a client domain?
We start from evidence, never from the content of the email. On the first day of an audit we pull four things: the public DNS records, the full headers of three recent messages, 30 days of bounce logs, and the spam rate from Postmaster Tools.
The cause is often visible in those four, and it is most often cause 1 or 2. One tax advisory firm on our case studies page had inbox placement of 59%, with SPF and DKIM aligned on only 68% of its mail. After the records and alignment were corrected and the unauthorized sending sources were found, alignment measured 99% and placement 93%.
The order matters. Fixing content while SPF is failing changes nothing, and warming up an IP while complaints run at 0.4% only burns the new IP.
How long does it take to get out of spam?
Authentication faults clear once the DNS change has spread, usually within 48 hours, because receivers check the records on every message. Reputation takes longer: in our work it is typically 2 to 6 weeks of clean sending before placement recovers, and longer after a blocklisting.
Recovery follows a fixed sequence:
- Stop the damage: pause the sends that are generating complaints or bounces.
- Repair authentication and alignment for every service that sends as your domain.
- Remove addresses that hard bounced and people who have not opened in 90 days.
- Resume at a fraction of the old volume, to your most engaged recipients first.
- Raise volume in steps while the spam rate stays under 0.10%.
No one can promise a date or an inbox rate, because the mailbox providers make the decision. What can be controlled is every input they measure.
If your records fail and you want them repaired, or they pass and mail still lands in spam, see what our email deliverability audit covers.
Drafted with AI assistance from our own records and client work, then reviewed and approved by Kunal Arora. See our editorial policy.