Why Are My Emails Going to Spam? Causes and Real Fixes

Emails go to spam for one of two reasons, depending on which side of the message you are on. If mail you want is landing in your spam folder, the filter has been mistrained — you fix that with "not spam" reports, a never-send-to-spam filter, and your contacts list. If mail you send is landing in other people's spam, the usual causes are missing authentication (SPF, DKIM, DMARC), a damaged sender reputation, and spam complaints — and since 2024, Gmail, Yahoo, and Microsoft enforce hard rules on all three. This guide fixes both problems.

One definition worth keeping: email deliverability is whether a message actually reaches the recipient's inbox rather than their spam folder — and it is earned through authentication, reputation, and recipient behavior, not granted at send time.

We are Flick (flicked.email), and we spend our days inside email headers — we build List-Unsubscribe parsing for a living. That work forces us to look at spam filtering from both directions, which is exactly what this question needs.

Which spam problem do you actually have?

"Why are my emails going to spam" describes two different situations, and almost every guide answers only one of them. Diagnose yours first.

	Receiving problem	Sending problem
Symptom	Mail you want (invoices, newsletters, a friend's messages) lands in your spam folder	Mail you send lands in other people's spam folders
Who controls the fix	Mostly you	Mostly you — but on the sender's side
Root cause	A mistrained or overcautious filter	Authentication, reputation, complaints
Time to fix	Minutes	Days to weeks
Where the fix lives	Your mail app's settings	Your DNS records and sending practices

If you are a normal inbox owner, read the next two sections. If you send email — a newsletter, a product, cold outreach, anything at volume — skip to the sender half. If you are both, welcome to our world.

Why is email I want landing in my spam folder?

Spam filters are trained to be paranoid, and with reason: 45.6% of global email traffic was spam in 2023. When roughly half of everything arriving at the gate is junk, the guard errs toward blocking. Wanted mail gets caught for a few predictable reasons.

The filter learned from the wrong signals. Filters learn from behavior across millions of inboxes. If enough other people marked a sender as spam — often because that sender made unsubscribing hard, more on that below — the filter starts junking that sender for everyone, including people who wanted the mail.

The sender broke the rules without knowing it. Since February 2024, Google requires bulk senders to authenticate with SPF, DKIM, and DMARC and to keep spam complaints below 0.3%. A newsletter you love that never set this up will land in your spam folder through no fault of yours — or theirs, beyond negligence.

You never interact with the sender. Filters watch engagement. Mail you consistently ignore drifts toward the spam folder over time, as Litmus notes in its breakdown of why email ends up in spam. The filter reads your indifference as a verdict.

Forwarding mangled the message. Auto-forwarded mail can fail the original sender's authentication checks, arriving at your inbox looking forged even when it is genuine.

How do I stop wanted emails going to spam?

Three fixes, in escalating order of strength. All take minutes.

1. Mark it "not spam." Open the spam folder, select the message, and report it as not spam. This is direct training data. One report may not be enough for a sender the filter distrusts globally — repeat it and the local signal eventually wins for your inbox.
2. Create a never-send-to-spam filter. In Gmail: search from: the sender's address, open the filter options, and check "Never send it to Spam." This is a standing order, not a suggestion — it overrides the spam classifier for that sender. Other providers have equivalents under filters or safe-sender lists.
3. Add the sender to your contacts. Most providers treat mail from your address book as presumptively wanted. It is the gentlest signal of the three, but it compounds with the other two.

One caution: only do this for senders you genuinely want. Rescuing everything from the spam folder retrains the filter to be useless. If what is in your spam folder is actually spam, leave it there — and see our guide on how to stop spam emails for the offense-side playbook.

Why are the emails I send going to other people's spam?

Now the harder half. When your outgoing mail lands in recipients' spam folders, the filter is judging you on five things, roughly in this order.

1. Authentication. SPF, DKIM, and DMARC are DNS records that prove your mail actually comes from your domain. Without them, you are indistinguishable from someone forging your domain, and modern filters treat unauthenticated mail accordingly. Google's sender guidelines require all three for anyone sending 5,000+ messages a day, and recommend them for everyone.

2. Spam complaint rate. Every time a recipient hits "report spam" on your mail, it counts against your domain — everywhere, not just at that provider. Google's enforcement threshold is a 0.3% complaint rate, with a recommendation to stay under 0.1%. That is three complaints per thousand delivered messages before enforcement begins. It is a small budget, and it is spent by your most annoyed recipients.

3. Sender reputation. Your domain and IP carry a history: complaint rates, bounce rates, spam-trap hits, engagement. Reputation decays slowly and recovers slower. Google Postmaster Tools shows you your standing with Gmail for free; most senders never look.

4. List quality and engagement. Sending to stale addresses produces bounces and spam-trap hits; sending to people who ignore you produces the low-engagement signal filters read as unwanted. Both erode reputation even with perfect authentication.

5. Sending patterns. Google explicitly advises sending at a consistent rate and avoiding bursts — sudden volume spikes from a quiet domain look like a compromised account or a spam run.

Notice what is missing from this list: "spammy words." Content filters exist, but the era when writing "free" in a subject line sent you to spam is over. Reputation and recipient behavior dominate. Fixing your word choice while your DMARC record is missing is rearranging deck chairs.

What do the Gmail, Yahoo, and Outlook bulk sender rules require?

Since 2024, the guessing game has ended: the major providers publish exactly what they require, and they enforce it.

Requirement	Gmail & Yahoo (Feb 2024)	Microsoft Outlook (May 2025)
Applies to	Senders of 5,000+ messages/day	Senders of 5,000+ messages/day
SPF + DKIM	Required	Required
DMARC	Required (at least p=none)	Required (at least p=none)
One-click unsubscribe	Required for marketing mail (RFC 8058)	Recommended: clearly visible opt-out
Spam complaint ceiling	Under 0.3%, aim under 0.1%	Not numerically specified
Consequence	Rejection or spam-foldering	Junk-foldering, then rejection of non-compliant mail

Microsoft initially planned to route non-compliant high-volume mail to Junk, then announced that starting May 5, 2025 it would be rejected outright with an access-denied error. These are not best practices anymore. They are conditions of delivery.

What is the most underrated cause of spam complaints?

Here is the part most deliverability guides skip: the single most preventable source of spam complaints is unsubscribe friction.

When a recipient wants out of your list, they will get out. The only question is which button they press. If your unsubscribe link is buried, broken, disguised in tiny pale grey type, or gated behind a login and a guilt-trip survey, the recipient uses the other exit — "report spam." In ZeroBounce's consumer research, 47% of people say they will file a spam complaint if an email gives them no way to unsubscribe, and 55% report mail as spam when the sender never asked permission in the first place.

Each of those complaints counts against the 0.3% budget. An unsubscribe costs a sender one subscriber. A spam complaint costs a sliver of reputation with every future recipient. Hard exits convert the first into the second, at scale, silently.

The fix has existed since 2017: RFC 8058, the one-click unsubscribe standard. It puts machine-readable List-Unsubscribe headers on the message so the mailbox provider itself can offer an unsubscribe button — no hunting through the footer, no login walls, no "are you sure." Gmail and Yahoo now require it from bulk senders, yet in Mailgun's deliverability survey only 33.1% of senders took steps to implement RFC 8058, and only 37% of those who made changes began closely monitoring their complaint rate. We wrote a full explainer on how one-click unsubscribe works under the hood.

This is where we should disclose our interest. Flick's one-swipe unsubscribe is built on exactly these headers — when a sender supports RFC 8058, our users leave a list with a single swipe, cleanly, and the sender gets an unsubscribe instead of a complaint. Because we parse these headers all day, we also grade the senders behind them: our Exit Gap Index at /graded scores real senders A–F on whether they honor unsubscribes. Senders who make leaving easy protect their own deliverability. Senders who trap subscribers are, complaint by complaint, filing themselves under spam. The numbers on how people actually leave lists are in our email unsubscribe statistics roundup.

How do I fix my outgoing email deliverability?

The checklist, in order of leverage:

1. Set up SPF, DKIM, and DMARC. Start DMARC at p=none to monitor without breaking anything. This is table stakes at Google and Microsoft alike.
2. Register for Postmaster Tools. You cannot manage a complaint rate you cannot see.
3. Implement one-click unsubscribe per RFC 8058, and honor requests promptly. Every easy exit is a complaint that never happens.
4. Prune your list. Remove addresses that have not engaged in months. Shrinking your list to people who want you is how the engagement signal turns positive.
5. Send at a consistent rate. No bursts, no long silences followed by blasts. Warm up new domains slowly.
6. Fix the appearance basics. 80% of consumers say they mark mail as spam based on how it looks at first glance — a real sender name, a coherent subject line, and a from-address on your actual domain are complaint prevention, not cosmetics.

FAQ

Should I unsubscribe from unwanted email or mark it as spam?

Unsubscribe from legitimate senders you once signed up for; mark as spam only what is actually spam. The spam button damages a sender's reputation with every mailbox provider, so it is the right tool for true spam and the wrong tool for a newsletter you are merely tired of. If the sender supports RFC 8058 one-click unsubscribe, leaving takes one click and you are cleanly out.

Does marking an email "not spam" actually work?

Yes — it is direct training data for your provider's filter, and for your inbox it usually wins within a few reports. For a sender with poor global reputation you may need to combine it with a never-send-to-spam filter and a contacts entry, because your local signal is competing with complaints from thousands of other inboxes.

What spam complaint rate is considered safe for senders?

Under 0.1%, per Google's sender guidelines — the 0.3% figure is where enforcement begins, not a target. That means fewer than one complaint per thousand delivered emails as the working budget. The cheapest way to stay under it is making unsubscribing effortless, so annoyed recipients leave without filing a complaint.

Why do my emails go to spam even with SPF, DKIM, and DMARC set up?

Authentication proves who you are; it does not prove you are wanted. Complaint rate, list quality, engagement, and sending patterns carry the rest of the verdict, which is why an authenticated sender with a stale list and a hidden unsubscribe link still lands in spam. Check your standing in Postmaster Tools — the dashboard usually names the problem.

How long does it take to recover from a spam reputation?

Weeks, typically, and only if the underlying cause is fixed first. Reputation is a moving average of recent behavior: authenticate, cut the unengaged addresses, add one-click unsubscribe, and send consistently, and the average slowly turns. There is no appeal process and no shortcut — providers trust the pattern, not the promise.