Why Emails Go to Spam: 10 Common Causes and How to Fix Each One

You wrote a good email, sent it to people who asked for it, and it still ended up in the spam folder. That is frustrating, but it is rarely random. Mailbox providers make filtering decisions from a stack of signals, and when mail is filtered, one or more of those signals is usually telling a clear story.

This guide walks through the ten causes we see most often, roughly in order of how frequently they show up, with a concrete fix for each. At the end you will find a diagnostic order to follow and a checklist you can work through in an afternoon.

How spam filtering decides your fate

Gmail, Outlook, Yahoo and Apple Mail do not rely on one rule. Each message is scored against a mix of signals, and the combined score decides whether it goes to the inbox, the spam folder, a secondary tab or gets rejected at the door. The main signal groups look like this:

No single row decides the outcome. One weak signal can be absorbed by strong ones elsewhere, but several weak signals together push you over the line.

Reason 1: Missing or broken authentication

Authentication is how a receiving server confirms you are who your From address says you are. Without it, the provider has no reason to trust your mail, and since the Google and Yahoo bulk sender rules took effect in February 2024 (followed by Microsoft’s Outlook rules for high-volume senders in May 2025), unauthenticated bulk mail is often rejected outright rather than just filtered.

The usual problems:

• No SPF record, or an SPF record with a syntax error or more than 10 DNS lookups
• DKIM signing not enabled at your ESP, or the public key missing from DNS
• A DKIM key shorter than recommended (use 2048-bit keys)
• No DMARC record, or a DMARC record that fails because neither SPF nor DKIM aligns with your From domain
• Two separate SPF records on the same domain, which invalidates both

Fix: Validate your policy with the DMARC Checker, count your SPF lookups and confirm your ESP is signing with DKIM. If you are unsure how the pieces fit together, the email authentication guide explains alignment in plain terms. A healthy baseline looks like this:

example.com.          TXT  "v=spf1 include:_spf.youresp.com -all"
sel1._domainkey.example.com.  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."
_dmarc.example.com.   TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Reason 2: Your IP or domain is on a blacklist

DNS blocklists (DNSBLs) track IPs and domains associated with spam. Many receiving servers query them on every connection, so a listing on a major list such as Spamhaus can block or filter a large share of your mail overnight.

Common triggers include complaints, spam trap hits, a compromised account or server, and sharing an IP pool with a bad sender.

Fix: Scan your domain and sending IPs with the Blacklist Checker. If you are listed, find and fix the cause before you request removal, because most operators will relist you quickly if the behavior continues. The blacklist removal guide covers the process for the major lists.

Reason 3: Weak sender reputation

Reputation is the provider’s memory of how your past mail was received. It attaches to your sending IP and, more and more, to your domain. Poor reputation is one of the strongest predictors of spam placement, and it is the one you cannot fix with a DNS change.

What drags reputation down:

• Spam complaints (“Report spam” clicks)
• Hard bounces from invalid addresses
• Mail to purchased, rented or scraped lists
• Long stretches of low engagement
• Irregular sending, with quiet weeks followed by huge blasts
• Past blacklist listings

Fix: Register your domain in Google Postmaster Tools, which shows how Gmail rates your domain and your real complaint rate. Rebuild by mailing only your most engaged segment for a few weeks and widening the audience slowly.

Reason 4: Content that looks like spam

Content filtering matters less than it did a decade ago, but it still works as a tiebreaker for senders with a middling reputation.

Patterns that raise risk:

• Subject lines in all caps or with multiple exclamation marks
• Clickbait subject lines that do not match the body
• Emails that are one large image with little or no live text
• Link shorteners such as bit.ly, which hide the real destination
• Links to domains with poor reputation of their own
• Broken or bloated HTML, embedded forms or scripts

Fix: Write subject lines that describe what is inside. Keep a healthy amount of real text next to images, link to full URLs on your own domain, and send a plain test version to see whether the problem follows the content or persists without it.

Reason 5: High bounce rates

Every bounce tells the provider something about how you manage your list. A few are normal. Many suggest you are mailing addresses you never confirmed or have not cleaned in years.

Keep hard bounces below 2% per campaign. Consistently going above that invites filtering and can lead to listings. The bounce rate guide explains how to read the codes.

Fix: Use double opt-in for new signups, verify imported lists before the first send and remove hard bounces immediately.

Reason 6: Low engagement

Gmail in particular leans heavily on how recipients react. If people consistently ignore, delete unread or never open your mail, the provider concludes it is unwanted and starts routing more of it to spam, including for the subscribers who do care.

Providers watch clicks, replies, “not spam” rescues, reading time and deletes without opening. Apple Mail Privacy Protection has made opens unreliable, so track clicks and replies instead.

Fix: Segment by engagement and send your highest-frequency campaigns only to recently active subscribers. Put people who have not clicked in 90 to 180 days into a re-engagement flow and suppress those who do not respond. The sunset policy guide shows how to build one.

Reason 7: No easy way to unsubscribe

If leaving is hard, people press the spam button instead. That turns a harmless unsubscribe into a complaint that directly lowers your reputation.

Since 2024, Google and Yahoo require bulk senders to support one-click unsubscribe (RFC 8058) through the List-Unsubscribe and List-Unsubscribe-Post headers, and to process requests within two days. Laws such as CAN-SPAM, GDPR and CASL also require a working opt-out.

List-Unsubscribe: <https://example.com/unsub?id=abc123>, <mailto:unsub@example.com>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

Fix: Add both headers, keep a visible unsubscribe link in the footer and honor requests immediately rather than waiting for the two-day limit.

Reason 8: Sudden volume spikes

If your domain normally sends 2,000 emails a day and suddenly sends 80,000, the provider sees a pattern that looks a lot like a hijacked account or a spam run. Filters become stricter until your behavior settles.

Fix: Grow volume gradually. When you move to a new IP or domain, follow a warmup plan like the one in the IP and domain warmup guide. For large announcements, spread the send across several hours or days and lead with your most engaged segment.

Reason 9: Hitting spam traps

Spam traps are addresses run by blocklist operators and mailbox providers to catch senders with poor list practices. You will never be told which addresses are traps.

• Pristine traps were never used by a real person. They only appear on web pages and in data that gets scraped, so mailing one means your list came from harvesting or a purchased file.
• Recycled traps were real addresses that were abandoned, left to bounce for a while and then turned into traps. Mailing one means you are not removing dead addresses.
• Typo traps sit on misspelled domains such as gmial.com and catch senders who do not validate signups.

Fix: Never buy or rent lists, confirm new subscribers with double opt-in, verify lists before importing them and remove long-inactive contacts. Our list hygiene guide covers a quarterly cleaning routine.

Reason 10: Technical misconfiguration

Beyond authentication, a handful of infrastructure details can hurt placement:

• Reverse DNS: your sending IP needs a PTR record that resolves to a hostname, and that hostname should resolve back to the same IP. Check it with the Reverse DNS Checker.
• HELO/EHLO hostname: the server should introduce itself with a valid, resolvable name.
• TLS: unencrypted SMTP connections are increasingly penalized, and Gmail visibly flags them.
• Shared IP pools: on entry-level plans, other senders on the same IP affect your results.

Fix: If you run your own mail server, audit these items. If you use an ESP, confirm they handle rDNS and TLS and ask which IP pool you are on.

How to diagnose and fix the problem

Work in a fixed order. Authentication issues mask everything else, so there is no point tuning content while DMARC is failing.

1. Run a full setup check first. Start with the Sender Reputation Checker, which looks at authentication, blacklists and DNS together and tells you where to dig.
2. Confirm each authentication record. Fix any SPF, DKIM or DMARC failures and confirm alignment.
3. Scan blacklists. Resolve the cause, then request delisting.
4. Read real headers. Send a test to Gmail and Outlook accounts, view the original message and check the Authentication-Results line. The Header Analyzer makes this easy.
5. Review list metrics. Look at bounce rate, complaint rate and click trends by mailbox provider in your ESP dashboard.
6. Test content last. Send a plain-text version of the same campaign and see whether placement changes.

If you send through a reputable ESP, much of this work is handled for you. Platforms such as SendPulse, Brevo and Mailchimp walk you through SPF, DKIM and DMARC setup for your own domain and automatically suppress hard bounces, complaints and unsubscribes, so the most common self-inflicted problems are harder to create. They cannot fix a purchased list or a poor sending pattern, though. That part stays your job.

Quick fix checklist

Use this list as a working document. Each item maps back to one of the ten causes above.

Most spam problems come from two or three of these at once. For the broader long-term picture, read the guide to improving email deliverability.