Why do emails sometimes end up in the spam folder?
Published 10 May 2025
Updated 4 Oct 2026
11 min read
Summarize with
Updated on 4 Oct 2026: We clarified bulk sender rules and added steps for recipients whose legitimate mail keeps landing in spam.
Emails end up in the spam or junk folder because mailbox providers combine many signals before deciding where to place a message. Common causes include failed or weak authentication, poor domain or IP reputation, high complaint rates, low engagement, risky content, sudden sending changes, poor list quality, and individual mailbox preferences.
A message can pass SPF, DKIM, and DMARC and still go to spam. Authentication verifies a domain identity used by the message. It does not prove that recipients want the message, that the sender has a clean history, or that this specific mailbox sees the sender as useful.
Treat spam placement as the result of several checks, including provider rules and reputation signals. A single authentication failure can be decisive, while other cases involve a pattern of weaker signals: a new domain, uneven volume, an old list, low engagement, or recent complaints.
Why emails go to spam
Spam filtering is not one universal rule. Gmail, Microsoft 365, Yahoo, and corporate gateways each make placement decisions with their own models. Those models weigh technical setup, sending history, recipient behavior, message content, and local user actions.
- SPF, DKIM, or DMARC failures make a message harder to trust, especially for domains that spoofers target.
- Mailbox providers build reputation for domains, IPs, sending systems, links, and message patterns.
- When recipients hit spam, that is a strong negative signal, even when the email is technically legitimate.
- Repeated ignores and spam reports indicate weak audience fit; sender open rates alone are an unreliable measure of engagement.
- Misleading subject lines, link-heavy copy, broken HTML, and suspicious redirects increase filtering risk.
- A single mailbox can have local rules, previous user actions, or personal models that differ from global placement.
A single spam-folder example is useful evidence, but it is not a full deliverability diagnosis. Look for patterns across providers, seed inboxes, campaign types, domains, and time windows before changing infrastructure.
How mailbox providers decide
Mailbox providers filter mail to protect recipients first. Legitimate senders do not get a permanent pass. Even a large company can see some of its own mail filtered if recipients report it or if a campaign looks risky compared with past behavior.
Five email spam filtering signals: authentication, reputation, complaints, engagement, and content.
The same campaign can land in the inbox for one recipient and spam for another. Providers combine global sender signals with recipient-level history. Previous positive actions, such as reading or moving a message to the inbox, can help explain different placement at different mailboxes. A Promotions tab placement or an SMTP rejection is a separate outcome from delivery to the spam folder.
|
|
|
|---|---|---|
DMARC fail | Domain identity did not align | Inspect SPF or DKIM alignment |
Complaints | Recipients report unwanted mail | Review consent and recent sends |
Low engagement | Audience fit is weak | Review segments and inactive recipients |
Volume spike | Sending pattern changed | Compare daily volume by source |
Blocklist or blacklist listing | IP or domain reputation needs review | Identify the listed source and cause |
Common spam signals and the next check for each.
What recipients can do with a legitimate email
If a message you expected lands in spam, first verify the sender address and message before treating it as safe. A display name alone does not establish who sent it.
- Move a verified message out of spam and use the mailbox provider's "Not spam" control. This gives the provider direct feedback for your mailbox.
- Add the verified sender to your contacts or safe senders list. In Gmail, a filter can also keep mail from a specific sender out of Spam.
- Check blocked senders, local rules, and any mail app that processes the account. A rule can move a message even when the sender is trusted.
- For a work or school mailbox, ask the mail administrator to inspect quarantine and organization-wide filtering if the message keeps disappearing or returning to junk.
A safe senders entry in Outlook does not always override filtering applied by Exchange or Exchange Online. If the same sender reaches other people but not your mailbox, start with your account settings and your administrator before asking the sender to change its entire sending setup.
Authentication still matters
SPF, DKIM, and DMARC do not guarantee inbox placement, but weak authentication makes every other problem harder. If a provider cannot verify the domain used by a message, it has less reason to trust it, especially when the message asks for a click, a payment, a login, or a reply.
The first technical check is simple: confirm that the message passes SPF or DKIM, and that at least one passing identifier aligns with the visible From domain under DMARC. Check every legitimate sending source because a single misconfigured platform can create a stream of DMARC failures.
Illustrative DNS TXT record valuesdns
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com v=spf1 include:_spf.example.net -all
These example values are illustrative; use the SPF mechanisms and report address for your own sending setup. Monitor authentication continuously because senders change. New marketing and billing systems often start sending before anyone has verified SPF, DKIM, or DMARC domain matching. That is why DMARC monitoring matters for ongoing deliverability and spoofing protection.
Passing authentication
- The provider can verify the domain used to authenticate the message.
- A passing SPF or DKIM domain aligns with the visible From domain.
- The message clears a core identity check.
Still going to spam
- The domain or IP has weak historical performance.
- Recipients ignore or report the mail.
- The campaign pattern looks unusual for that sender.
Reputation and complaints
Reputation is the history mailbox providers build about a sender. It includes domain and IP history, complaint patterns, bounce rates, spam trap hits, recipient engagement, link reputation, and the consistency of sending behavior.
Complaint rate matters because it is direct feedback. If enough recipients use the spam button, the provider has a clear reason to protect similar recipients from future messages. This explains why a legitimate newsletter, product update, or account notice can hit spam if the audience did not expect it or does not value it.
Complaint signal severity
Use these qualitative bands to triage risk across campaigns; provider complaint-rate limits are covered below.
Healthy
Low
Few complaints and steady engagement.
Watch
Rising
Complaints rise after a list or content change.
Critical
High
Complaints affect more than one provider or campaign.
A blocklist or blacklist listing is another reputation signal, but it needs context. Some blocklists affect business mail more than others. Listings can point to compromised infrastructure, poor list acquisition, shared IP abuse, or an unknown sending source.
For that workflow, blocklist monitoring helps connect a blacklist event with the campaign, IP, or sender involved. Investigate the cause before requesting removal.
Remove hard-bounced addresses promptly and honor unsubscribes before the next send. Review how addresses were collected; old imports and purchased lists often produce complaints and invalid recipients.
Content and sending patterns
Content problems rarely mean a single forbidden word caused spam placement. Filters evaluate the whole message: subject line, links, domain age, HTML quality, tracking patterns, unsubscribe handling, sender identity, and whether the message matches what recipients previously engaged with.
- Avoid misleading urgency, fake replies, and subject line claims the body does not support.
- Keep link domains consistent with the sender and avoid chained redirects.
- Fix broken markup, huge images, invisible text, and missing plain-text versions.
- Avoid sharp volume jumps after a long pause. Do not send to purchased lists.
- Send to people who asked for the mail and can recognize the brand.
Sending frequency also matters. A new domain that sends a few hundred messages one week and tens of thousands the next looks different from a domain with a steady history. Send first to people who recently engaged, then expand volume as delivery and complaint data remain healthy.
Do not fix spam placement by changing everything at once. If DNS, sender name, template, list source, link tracking, and volume all change together, you lose the ability to see which change helped or hurt.
Bulk sender requirements that affect placement
High-volume senders need to meet provider-specific baselines. Gmail treats a domain as a bulk sender after about 5,000 messages to personal Gmail accounts in 24 hours, and that classification does not expire. Outlook.com applies stronger authentication requirements to domains sending more than 5,000 messages a day to Microsoft consumer addresses. Yahoo also has specific requirements for bulk senders.
- For bulk traffic, configure SPF and DKIM, publish DMARC, and make sure a passing SPF or DKIM identity aligns with the visible From domain. Outlook.com also requires SPF and DKIM to pass.
- For Gmail delivery, maintain valid forward and reverse DNS, use TLS, and format messages according to RFC 5322.
- Keep Gmail's user-reported spam rate below 0.1% and avoid reaching 0.3% or higher. Yahoo requires bulk senders to stay below 0.3%.
- For Gmail bulk marketing and subscribed mail, implement RFC 8058 one-click unsubscribe and a visible body link. Yahoo requires easy unsubscribe for marketing mail and requests honored within two days; Gmail recommends processing requests within 48 hours.
- Identify promotional and transactional traffic clearly, and apply the relevant consent and unsubscribe rules to each message type.
These requirements are a delivery baseline, not an inbox guarantee. Noncompliant mail can be filtered, rate-limited, or rejected. Outlook.com rejects high-volume mail that fails its authentication requirements with a 550 5.7.515 error. Compliant mail can still reach spam when reputation or recipient feedback is poor.
A practical diagnosis workflow
When emails are going to spam, start with the message that failed. Headers, authentication results, sending source, recipient provider, campaign timing, and list segment usually narrow the issue quickly.
Email spam placement diagnosis flow from message headers to one controlled change.
- Pull the full headers from the spammed message and read the authentication results.
- Confirm which platform, IP, return-path, and DKIM selector sent the message.
- Compare affected providers, campaigns, segments, and time windows.
- Review complaints, bounces, blocklist or blacklist events, and recent volume changes.
- Test the exact subject, body, links, HTML, and unsubscribe path.
- Adjust one major variable at a time, then measure the next send.
For a real message test, send the same email through the email tester and inspect the authentication result and content issues before changing DNS or copy.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Check the domain as a whole too, because one message can expose a wider setup issue. A domain health review catches common SPF, DKIM, and DMARC problems before they turn into repeat placement failures.
Where Suped fits
Suped is our DMARC reporting and email authentication platform. When spam placement repeats, its DMARC reports help identify which sources pass or fail authentication, while blocklist alerts flag reputation events that need investigation.
Issues page showing top issues, verified sources, unverified sources, and authentication pass rates
In Suped, teams can use that data to verify a sending source, fix a DKIM selector, remove an unauthorized sender, resolve an SPF lookup problem, or move a DMARC policy forward after legitimate traffic is authenticated.
Manual approach
- Headers, DNS records, reports, and blacklist checks live in separate places.
- Marketing, IT, and vendors need to agree on which source sent the mail.
- Teams often discover issues after a campaign has been filtered.
Suped workflow
- Review DMARC, SPF, DKIM, and blocklist status together.
- Separate known sending sources from sources that need verification.
- Use alerts to spot authentication and reputation changes.
Suped also has hosted DMARC, hosted SPF, SPF flattening, hosted MTA-STS, alerts, and multi-tenant reporting for teams that manage many domains or need to advance policy enforcement with fewer manual DNS edits.
Views from the trenches
Best practices
Check authentication, reputation, complaints, and content before changing DNS records or copy.
Use many inboxes and providers before treating one spam placement as a domain-wide failure.
Keep send patterns steady so providers can compare new campaigns against trusted history.
Common pitfalls
Treating one spam-folder screenshot as proof of a deliverability failure everywhere.
Assuming authenticated mail must reach the inbox when complaint signals are negative.
Changing DNS, content, list source, and volume together, then losing cause and effect.
Expert tips
Separate personal mailbox behavior from global sender reputation before taking action.
Compare spam placement with campaign timing, audience quality, and complaint history.
Investigate internal or trusted senders with the same rigor as any outside sender.
Marketer view
Marketer from Email Geeks says a single mailbox spam placement is worth checking, but it does not prove that every recipient sees the same result.
2023-10-26 - Email Geeks
Marketer view
Marketer from Email Geeks says webmail placement can happen inside the provider's own interface, even with no third-party filtering involved.
2023-10-26 - Email Geeks
What to fix first
The first fix depends on the evidence. If authentication fails, fix SPF, DKIM, and DMARC domain matching first. If authentication passes, focus on reputation, complaints, engagement, content, and sending pattern changes.
Identify the affected source, confirm the technical setup, compare provider behavior, clean the audience, reduce complaint risk, and change one major variable at a time. Spam placement improves when the sender becomes easier to trust and recipients give providers better signals.
