Why are my emails landing in spam?

Quick answer

Your emails are landing in spam because receiving servers do not yet trust the combination of your domain, your mailbox and your sending pattern. In practice that is almost always one of five things: SPF, DKIM or DMARC is failing; the domain or mailbox is too new for the volume being sent; bounce or spam-complaint rates are elevated; recipients are ignoring or deleting your mail; or the copy is templated, link-heavy and image-heavy. Fix them in that order — authentication first, list quality second, volume and copy third — and placement recovers over days, not minutes.

Spam placement is not a mystery and it is rarely one big mistake. It is a trust score, and every cause below moves it in a predictable direction.

Delivery and placement are also not the same thing. A message can be accepted by the receiving server, counted as delivered in your analytics, and still be filed in spam. Nothing in any sending tool reports placement directly, because receiving providers never tell the sender which folder a message landed in. That is why diagnosis works backwards: you check the signals filters use, in the order they carry weight.

What causes emails to land in spam?

Emails land in spam when the receiving mail server accepts the message but decides it does not trust the sender enough to show it. Filters weigh six signals:

• Authentication — SPF, DKIM and DMARC must pass and align with your sending domain.
• Domain and mailbox reputation — built slowly by real sending history, lost quickly.
• List quality — invalid addresses, spam traps and stale contacts produce bounces and complaints.
• Engagement rate — replies and opens weighed against deletions, "mark as spam" and ignores.
• Volume pattern — steady and modest beats spiky. A cold mailbox jumping to hundreds of sends a day is the classic trigger.
• Content — link count, images, attachments, tracking, and how obviously templated it reads.

No single signal decides placement. A well-authenticated domain with a 12% bounce rate still lands in spam, and a spotless list on an unauthenticated domain does too.

Which cause is most common in cold outreach?

Authentication and list quality, in that order. Most "the tool has a deliverability problem" reports turn out to be a partially failing DKIM record or a purchased list that was never verified.

How do I narrow it down quickly?

Answer four questions before changing anything:

1. Does every DNS record show Verified, checked today rather than remembered from setup?
2. What is the campaign's bounce rate over the last seven days?
3. How old is the domain, and has warmup finished on the mailbox?
4. Did placement fall on a specific date, or has it always been poor?

A sudden drop points to a change — DNS, a new import, a volume jump. Consistently poor placement from day one points to authentication or a domain that is too new.

How do I check whether SPF, DKIM and DMARC are passing?

Open Email Accounts and look at your domain rows. Each domain shows SPF, DKIM and DMARC badges, and only reaches Ready to send when all of them pass. Use DNS records for the exact values and Re-check (or Verify domain) to test DNS again.

You can confirm independently from a terminal:

• dig TXT yourdomain.com — your single SPF record
• dig TXT selector._domainkey.yourdomain.com — DKIM
• dig TXT _dmarc.yourdomain.com — DMARC

What does each DNS status actually mean?

• Pending — the record has not been found yet. Either it was never added, or DNS has not propagated. Propagation is usually minutes and occasionally up to 48 hours, so re-check after an hour before assuming something is wrong.
• Verified — the record was found and its value matches what MunchReach expects. This is the only status that counts. Verified today does not mean verified next month: DNS edits elsewhere in your account can silently break it.
• Failed — the record exists but its value is wrong, incomplete, or duplicated. A failure is more urgent than a pending record, because it usually means a typo you will not spot by re-reading the dashboard.

Ready to send is a summary of all three, not a fourth record. If it does not appear, one badge beside it is not verified.

How do I interpret a failure on each specific record?

• SPF failed — most often two SPF records on the same domain, or a lookup limit exceeded because too many services are chained in. A domain is allowed exactly one v=spf1 TXT record; merge the include mechanisms into it.
• DKIM failed — nearly always a truncated or wrapped key value, or a host that appended your domain a second time. Compare the first and last 10 characters of the published value against the value shown in MunchReach.
• DKIM pending while SPF is verified — the DKIM record was added at the wrong host name. It must sit at the exact selector shown, not at the root.
• DMARC failed — usually a malformed policy string. Start with v=DMARC1; p=none; rua=mailto:you@yourdomain.com, confirm it verifies, then tighten to p=quarantine once reports look clean.
• Everything verified but mail still filed as spam — authentication is no longer your problem. Move on to list quality and volume; do not keep editing DNS.

What breaks authentication most often?

1. Two SPF records. More than one SPF record on a domain is a hard failure, not redundancy. Merge them into one.
2. A truncated DKIM value. The key is long and paste often clips it. Re-copy the whole string.
3. The domain appended twice. Some DNS hosts add the domain for you, producing selector._domainkey.example.com.example.com.

If you changed DNS providers or tidied records recently, re-check the domain — authentication breaks silently. Full detail lives in SPF, DKIM and DMARC explained.

Is my domain or mailbox too new for the volume I am sending?

Probably, if the domain is under a month old or the mailbox has not completed warmup. A brand-new domain has no reputation at all, so filters default to suspicion and watch how you behave.

What to do:

• Leave warmup running on every new mailbox and check its health band in Warmup.
• Keep each mailbox's Daily limit modest — the default of 50 exists for a reason.
• Scale by adding mailboxes, not by raising one mailbox's limit. See how sending limits work.
• Use a dedicated outreach domain or subdomain, never your main corporate domain.

Does a pause in sending hurt reputation?

A short pause does not hurt. Erratic sending does: 400 emails on Monday, nothing for a week, then 600 on Tuesday reads as a burst pattern. Consistency is the signal.

How do I tell a warmup problem from a reputation problem?

Warmup problems affect new mailboxes and improve week by week as volume stays flat. Reputation problems affect established mailboxes and follow an event you can date — a bad import, a spike, a broken DNS record. If an older mailbox on the same domain also degraded at the same time, treat it as a domain-level reputation issue and reduce volume across every mailbox on that domain, not just the loudest one.

Are bounces and spam complaints dragging my placement down?

Yes, faster than anything else on this list. Bounces tell the receiver you are mailing addresses you never verified, and complaints tell it recipients do not want your mail.

Targets to hold:

• Hard bounces: under 2%
• Spam complaints: under 0.1%
• Unsubscribes: watch the trend rather than a threshold

MunchReach has a hard safety net on top of those targets. Once a campaign or mailbox exceeds 8% bounces or 0.5% complaints across a rolling 24 hours — measured after at least 20 sends — it is paused automatically, with the reason recorded and the workspace notified. If you see a campaign paused with a deliverability reason, that guard fired.

How do I bring bounce rate down?

1. Verify the list before importing it, and answer Is this list verified? honestly during import.
2. Remove everything that has already bounced; a hard bounce never becomes valid later.
3. Drop role addresses (info@, sales@, support@) and anything older than about 12 months.
4. Re-launch at lower volume once the list is clean.

More detail: reducing your bounce rate.

What if bounces are concentrated on one provider or domain?

Group the bounces before reacting. Many bounces at a single recipient domain usually means that company's gateway is blocking you specifically — exclude it and move on. Bounces spread evenly across providers point at the list itself. Bounces that all began on one date point at the import made that day, so remove that batch rather than pruning the whole list.

Does my email copy trigger spam filters?

Copy alone rarely sends a well-authenticated email to spam, but it decides borderline cases — and cold first-touch emails are usually borderline. Filters and recipients react to the same things.

For a first email:

• One link maximum. Zero is fine.
• No images, no attachments, no tracking pixels you do not need.
• Short. Under 120 words reads human; a formatted layout reads like marketing.
• Specific. A real reason for contacting this person outperforms any subject-line trick.
• Plain formatting. Skip coloured buttons, big headers and multi-column HTML.

Do "spam trigger words" still matter?

Barely, and far less than people believe. Modern filters score behaviour and reputation, not a banned-word list. Writing "free" or "guarantee" will not send a trusted sender to spam — but a message stacked with urgency, capitals and exclamation marks correlates with everything else filters dislike, so restraint still pays.

Does open and click tracking hurt placement?

Slightly. Tracking adds an image pixel and rewrites links through a redirect, and a redirect on an unrecognised host looks worse than a link to your own domain. Two mitigations: run tracking on your own custom tracking domain, and consider sending the first email untracked, treating replies as the real signal.

How do I test whether the copy is the cause?

Isolate one variable. Send the same audience segment two versions from the same warm mailbox on the same day — one as written, one stripped to plain text with no links — and compare reply rate over the following week. If both perform identically, the copy was never the problem and the cause sits upstream in authentication, reputation or list quality.

Am I on a blacklist?

Possibly, and it is worth ruling out — but blacklisting is a symptom, not the root cause. Domains and sending IPs get listed after sustained bounces, complaints or spam-trap hits, so the fix is always the underlying behaviour.

Check your domain and sending IP against a public list checker such as MXToolbox. If you are listed:

1. Stop sending from the affected domain immediately.
2. Clean the list and repair authentication.
3. Follow the list's own delisting request process.
4. Resume at very low volume, and expect weeks rather than days.

Why do my emails land in spam at one provider only?

Because each provider scores you separately. Placement at Google, Microsoft and smaller business hosts can differ sharply from the same mailbox on the same day.

• Google only — usually engagement. Replies are low, deletions are high, or tracking is heavy. Also check the Promotions tab before assuming spam.
• Microsoft only — Outlook and Microsoft 365 weight domain age and volume consistency harder than most. Reduce per-mailbox volume, extend warmup, and be patient; recovery here is slower.
• Small business hosts only — often a strict third-party gateway with its own list. Look for a bounce message naming the filtering service and follow its delisting process.
• Every provider — authentication or list quality. Go back to the domain badges and the bounce rate.

How do I fix spam placement, step by step?

Work in this order. Skipping ahead wastes the effort you spend later.

1. Repair authentication. Get SPF, DKIM and DMARC to Verified and the domain to Ready to send.
2. Clean the list. Remove bounces, role addresses and unverified imports.
3. Cut volume per mailbox and widen the sending window so sends spread out.
4. Let warmup run longer before pushing volume back up.
5. Rewrite the first email — one link, no images, under 120 words, specific.
6. Add mailboxes rather than raising limits when you need more volume.
7. Re-test placement by sending yourself a message at two or three different mail providers.
8. Watch replies, not opens. Opens are unreliable in both directions; replies are the honest measure.

Change one thing at a time and give each change a week. Deliverability moves slowly enough that stacking five simultaneous fixes leaves you unable to tell which one helped.

How long does recovery take?

Usually one to three weeks of clean, modest, consistent sending. Reputation is earned back at the same slow rate it was built, and there is no reset button — which is also why a burned domain is often cheaper to replace than to rehabilitate.

Which numbers should I watch during recovery?

Reply rate first, bounce rate second, unsubscribe trend third. A recovering domain shows replies returning before any other metric moves. Ignore open rate while you diagnose — privacy proxies inflate it and image blocking suppresses it, so it can rise while placement gets worse.

When should I contact support?

Contact support when authentication is fully verified, your bounce rate is low, mailboxes are warm and inside their limits, volume is modest, and mail still lands in spam consistently across several providers. Include the campaign name, the affected mailbox and where your test messages landed — that is enough to investigate the sending path.

Frequently asked questions

Is Gmail's Promotions tab the same as spam?

No. Promotions is still the inbox and the message was delivered, but plain-text-style formatting, fewer links and no images all push a cold email towards the Primary tab.

Will sending fewer emails per day on its own fix spam placement?

Only if volume was the problem. Lower volume from a domain with failing SPF or DKIM still lands in spam, so verify authentication before you touch limits.

Should I use a separate domain for cold outreach?

Yes. Use a dedicated domain or subdomain so that a reputation problem never reaches the domain your invoices, contracts and support email depend on.

Does one spam complaint matter?

One does not, but the rate does. Complaints above roughly 0.1% of sends are damaging, and MunchReach automatically pauses sending once complaints pass 0.5% over a rolling 24-hour window.

Can I test where my email lands before launching a campaign?

Send yourself the exact email at two or three providers — one consumer address and one business address — and check the inbox, Promotions and spam folders in each. Placement varies by provider, so a single test address proves little.

Why did placement drop suddenly on a campaign that used to work?

The usual causes are a DNS change that broke authentication, a newly imported unverified list, or a volume jump. Check the domain authentication badges first, then the bounce rate for the exact days placement fell.