If you have emails going to junk in Outlook, the cause is almost always one of three things: your domain fails Microsoft's authentication checks, your sending IP or domain has a poor reputation at Microsoft, or Microsoft 365 classifies your message as bulk mail with a high complaint level. The fix depends on which one it is, and the message header tells you. This guide shows how to read it, how Outlook.com and Microsoft 365 filter differently, and what senders and recipients can each do.
One thing to settle first: "Outlook" is two filtering systems. Consumer mailboxes (outlook.com, hotmail.com, live.com) are filtered by Microsoft centrally; on Microsoft 365, every company's admin can change thresholds, allow lists and policies.
Key takeaways
- Read the header before changing anything:
Authentication-Results,CAT,SFVandBCLtell you whether the problem is authentication, reputation or bulk classification. - Outlook.com bulk rules are enforced: since May 5, 2025, domains sending more than 5,000 emails a day to Outlook.com addresses need SPF, DKIM and DMARC (at least
p=none) aligned with SPF or DKIM. - Microsoft 365 is per tenant: each organization sets its own bulk threshold (BCL 7 by default, 6 or 5 in the preset policies), so the same email can land in the inbox at one company and in Junk at another.
- SNDS and JMRP only help if you own the IPs: on a shared IP pool, your ESP holds that data, not you.
- Safe sender lists are a recipient workaround: they help one mailbox and do not bypass Microsoft's authentication enforcement.
Outlook.com vs Microsoft 365: two different junk filters
Both systems run on Microsoft's filtering stack (Exchange Online Protection), but who controls the settings differs, and that changes what you can fix.
| Outlook.com / Hotmail (consumer) | Microsoft 365 (business) | |
|---|---|---|
| Who sets the filter | Microsoft, the same for every user | Microsoft defaults, then each tenant's admin |
| Bulk mail handling | Microsoft decides | Admin-set BCL threshold: 7 by default, 6 (Standard preset), 5 (Strict preset) |
| High-volume sender rules (May 2025) | Apply | Microsoft's announcement covers the consumer service only |
| Where filtered mail goes | Junk Email folder, or rejected at SMTP | Junk Email folder or quarantine, depending on policy |
| Recipient fixes | Not junk, Safe senders, contacts | The same, plus admin allow entries and mail flow rules |
| Sender data available | SNDS and JMRP (for IPs you control) | Nothing tenant-specific; you only see bounces and headers |
In practice, B2C senders mostly fight Outlook.com reputation, while B2B senders fight a patchwork of tenant policies. If only some business recipients see Junk, the difference is often their admin's settings.
Microsoft 365 also has a newer layer: a Promotions folder. Microsoft's bulk complaint level documentation says that, as of July 2026, bulk messages that are promotional get a Promotions tag, and admins can turn on Bulk moves enabled so that bulk mail below the junk threshold goes to a Promotions folder instead of the inbox. If a business recipient says your newsletter "disappeared" but it is not in Junk, check there.
Microsoft's high-volume sender requirements
In April 2025 Microsoft announced requirements for high-volume senders to Outlook.com consumer addresses, effective May 5, 2025. If your domain sends more than 5,000 emails per day to outlook.com, hotmail.com and live.com addresses, it must have:
- SPF that passes for the sending domain.
- DKIM that passes.
- DMARC published with at least
p=none, aligned with SPF or DKIM (Microsoft says preferably both).
Microsoft also expects a reply-capable From or Reply-To address, a working unsubscribe link and regular removal of invalid addresses.
Junk or rejection? What Microsoft actually says
Microsoft's wording differs between pages, so plan for both outcomes. The announcement (updated April 29, 2025) says that after May 5, 2025, non-compliant mail from high-volume domains is routed to Junk first, and that rejection will follow at a date to be announced. The Outlook.com postmaster policies page describes the same order: junk first, rejection if problems persist. Meanwhile, Microsoft's support article Fix NDR error "550 5.7.515" in Outlook.com treats the rejection as something senders already receive. The rejection text is:
550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.So a non-compliant high-volume domain can see either symptom: messages quietly landing in Junk, or hard bounces with 5.7.515. If you see that code, the problem is authentication, full stop. No content change or warm-up will fix it. The announcement also notes that recipients' Safe Senders lists do not bypass this enforcement.
The rules mirror what Gmail and Yahoo require from bulk senders. Our bulk sender requirements guide compares all three side by side, and the SPF, DKIM and DMARC setup guide walks through the DNS records.
How to read the headers of an email that went to junk in Outlook
Ask a recipient who got your email in Junk to send you the full headers, or send a test to your own Outlook.com and Microsoft 365 mailboxes. In Outlook on the web, open the message, select the three-dot menu, then View and View message details. In classic Outlook for Windows, open the message and go to File, Properties, Internet headers. Paste the result into Microsoft's free Message Header Analyzer if you want it parsed.
Three headers matter. Microsoft documents them in its anti-spam message headers reference:
- Authentication-Results: SPF, DKIM and DMARC results, plus
compauth, Microsoft's composite authentication verdict with a three-digit reason code. - X-Forefront-Antispam-Report: the filtering verdict.
CATis the category that acted on the message,SFVis the spam filter verdict,CIPis the connecting IP. - X-Microsoft-Antispam: contains
BCL, the bulk complaint level from 0 to 9.
Worked example: authenticated, but junked as bulk
Authentication-Results: spf=pass (sender IP is 203.0.113.25) smtp.mailfrom=mail.example.com; dkim=pass (signature was verified) header.d=example.com; dmarc=pass action=none header.from=example.com; compauth=pass reason=100
X-Forefront-Antispam-Report: CIP:203.0.113.25;CTRY:US;LANG:en;SCL:5;SRV:BULK;IPV:NLI;SFV:SPM;H:mail.example.com;PTR:mail.example.com;CAT:BULK;
X-Microsoft-Antispam: BCL:7;Reading it: SPF, DKIM and DMARC all pass and compauth=pass reason=100 confirms alignment, so DNS is not the problem. IPV:NLI means the IP is not on Microsoft's IP reputation lists. The deciding values are CAT:BULK, SRV:BULK and BCL:7: Microsoft rates you as a bulk sender with a mixed level of complaints, and BCL 7 meets the default threshold, so the message went to Junk. The fix is engagement and complaints (who you send to, how often, how easy it is to unsubscribe), not DNS.
Worked example: authentication failure
Authentication-Results: spf=pass (sender IP is 198.51.100.7) smtp.mailfrom=bounces.esp-example.net; dkim=pass (signature was verified) header.d=esp-example.net; dmarc=none action=none header.from=example.com; compauth=fail reason=001
X-Forefront-Antispam-Report: CIP:198.51.100.7;...;SFV:SPM;...;CAT:SPOOF;SPF and DKIM pass, but for the provider's domain, not yours. Your From domain has no DMARC record and nothing aligns, so compauth=fail reason=001 and the category is SPOOF. The fix: custom DKIM signing with your own domain at your provider, plus a DMARC record.
Quick reference for the values you will see
| Value | Meaning | What to do |
|---|---|---|
SFV:NSPM | Not spam, delivered to the inbox | Nothing; if it is still in Junk, a user or inbox rule moved it |
SFV:SPM | Marked as spam by filtering | Check CAT to see why |
SFV:SFE / SFV:SKA | Allowed by the user's Safe Senders / admin allow list | The recipient-side fix is working |
CAT:BULK with high BCL | Bulk mail above the tenant's threshold | Reduce complaints, tighten targeting |
CAT:SPOOF, compauth=fail | From domain not authenticated | Align DKIM or SPF with your From domain, publish DMARC |
CAT:SPM / HSPM | Spam / high confidence spam by content and reputation | Check IP/domain reputation, content, links |
SCL and BCL: what the numbers mean now
Many older guides tell you to look at SCL (spam confidence level, -1 to 9). Microsoft now says that in cloud organizations SCL does not determine whether a message is spam or what happens to it. It mainly matters for on-premises Exchange. Use CAT and SFV for the verdict, and treat SCL as a hint at most.
BCL is different and very relevant for newsletters. Microsoft's scale:
| BCL | Microsoft's description | Typical outcome |
|---|---|---|
| 0 | Not from a bulk sender | Not filtered as bulk |
| 1–3 | Bulk sender that generates few complaints | Inbox under every default threshold |
| 4–7 | Bulk sender that generates a mixed number of complaints | 5 and above hits the Strict preset; 6 and above hits Standard; 7 hits the default policy |
| 8–9 | Bulk sender that generates a high number of complaints | Junk (or quarantine under Strict) in almost every tenant |
You cannot set your own BCL; Microsoft derives it from internal and external data about how recipients react to your mail. At BCL 6 or 7, a tenant using the Standard or Strict preset will junk or quarantine your newsletter even if everything else is fine.
SNDS and JMRP: Microsoft's sender data
Both programs still exist and are free, but they now live on a new portal: Smart Network Data Services (SNDS), which replaces the old sendersupport.olc.protection.outlook.com address. Microsoft says access no longer expires, so you do not need to re-confirm ownership.
What SNDS shows
- Filter result per IP per day: green when less than 10% of recipients got a spam verdict, yellow between 10% and 90%, red above 90%.
- Complaint rate: complaints divided by message recipients. Microsoft notes that more than 30% of IPs stay below 0.3%.
- Comments such as JMRP complaints, virus uploads or open proxy findings. Data is kept for 90 days.
How to enroll
- Sign in to SNDS with a Microsoft account.
- Request access to your IP range (or ASN).
- Microsoft sends an authorization email to addresses it finds itself:
postmaster@orabuse@at the domain in your IPs' reverse DNS, or the contacts in the IP's registry (RDAP) record. You cannot pick the address. - Confirm the link, then open View Data. Enroll in JMRP from the same portal.
JMRP (Junk Mail Reporting Program) sends you a copy of each message an Outlook.com user marks as junk. Use it to suppress complainers immediately.
How to fix emails going to junk in Outlook (senders)
Work through these in order; each step rules out a cause.
- Collect evidence. Get headers from at least one Outlook.com and one Microsoft 365 recipient, plus any bounces. Note the
5.7.xcodes exactly. - Fix authentication if
compauthfails or you see5.7.515. Your From domain must align with DKIM (best) or SPF, and DMARC must exist. Confirm in the header, not just in a DNS checker. - Check for blocks. A
550 5.7.606-649 Access denied, banned sending IPbounce from Microsoft 365 means your IP is on Microsoft's blocked senders list; request removal atsender.office.com(Microsoft says it can take 24 hours or longer). A5.7.511bounce means you must emaildelist@microsoft.comwith the full bounce. For Outlook.com consumer blocks (bounces mentioning a block list, often with a code such as S3150), use the Outlook.com sender support form linked from the postmaster site. - If bulk is the verdict, lower complaints. Stop mailing contacts who have not opened or clicked in 6 to 12 months, make the unsubscribe link obvious, honor one-click unsubscribe, and send less often to low-engagement segments. A smaller list with fewer complaints usually beats a big list at BCL 7. See how to clean an email list.
- Check reputation trends. If you have dedicated IPs, look at SNDS colors and complaint rates. For a broader check across Gmail, Microsoft and blocklists, follow our email sender reputation check.
- Ramp volume, do not spike it. New domains and IPs that jump to full volume look like a spammer to Microsoft. Use a gradual schedule like the one in our IP and domain warm-up guide.
- Review content last. Check link domains (shorteners, shared tracking domains), display names and image-only layouts. Content is rarely the root cause when the header shows
CAT:BULK.
If your problem is broader than Microsoft (Gmail and Yahoo filtering you too), start with the main guide on why your emails are going to spam, which covers causes across all providers.
What recipients and admins can do
These fix delivery for one mailbox or one organization. They do not repair a sender's reputation.
Outlook.com and personal Outlook users
- In the Junk Email folder, select the message and choose Not junk. This moves it and feeds Microsoft's filter.
- Add the address under Settings, Mail, Junk email, Safe senders and domains, then Save.
- Add the sender to your contacts; Outlook treats contacts as safe by default.
Microsoft 365 admins
Microsoft's allowlist guidance ranks the options from most to least recommended:
- Allow entries in the Tenant Allow/Block List (Microsoft Defender portal). Microsoft's first choice. Also submit the message to Microsoft as good mail, so the filter can learn.
- A mail flow rule that sets SCL to bypass spam filtering only when the sender domain matches and the
Authentication-Resultsheader containsdmarc=pass. Never use the domain alone as the condition, because anyone can spoof it. - Outlook Safe Senders per mailbox.
- IP Allow List in the connection filter, and only for small ranges you control. Microsoft warns against allowing shared infrastructure.
- Allowed senders/domains in anti-spam policies: testing only.
Malware and high confidence phishing are quarantined regardless of any allow list. Raising the BCL threshold also works, but lets more gray mail through for everyone.
A copy-paste checklist for B2B senders
When a business customer says "your emails go to our junk folder", send them this short request. It gets you the evidence and gives their admin the safe fix:
Hi [name], thanks for flagging this. Two things would help us fix it:
1) Could you forward the full message headers of one email that landed in Junk?
(Outlook on the web: open the email, ... menu, View, View message details.)
2) If your IT team manages Microsoft 365 filtering, they can add an allow entry
for [news@yourdomain.com] in the Tenant Allow/Block List and submit the
message to Microsoft as "not junk". Our mail passes SPF, DKIM and DMARC.On the sender side, eMailBase checks SPF, DKIM and DMARC on each sending domain and runs a spam-score check before a campaign goes out, so you catch authentication gaps before Microsoft does. No tool can change a recipient's tenant settings.
Frequently asked questions
Why do my emails go to junk in Outlook but not in Gmail?
Microsoft and Google keep separate reputation data and weigh signals differently. Microsoft's filter classifies newsletters with a complaint-based bulk level (BCL), and Microsoft 365 tenants add their own thresholds on top. A sender with acceptable Gmail engagement can still sit at BCL 6 or 7, which a strict tenant junks.
Does the 5,000 emails per day rule apply to Microsoft 365 business mailboxes?
Microsoft's announcement covers its consumer service: outlook.com, hotmail.com and live.com. Business tenants filter with their own anti-spam policies, which already penalize unauthenticated mail through composite authentication. In practice, set up SPF, DKIM and DMARC regardless of volume.
Why are my own emails going to junk in Outlook when I send to myself or colleagues?
Usually because the message failed authentication for your own domain, which Microsoft treats as self-to-self spoofing (reason code 601 or 010). A marketing tool sending as your domain without DKIM is the classic cause.
How long does it take to get out of Outlook's junk folder after fixing things?
Authentication fixes work on the next message. Reputation and BCL improve over weeks of lower complaints and steady volume. Microsoft's delist portal says removal from its blocked senders list can take 24 hours or longer.
Is the Focused Inbox's "Other" tab the same as junk?
No. Other is still the inbox, sorted by Focused Inbox; Junk is a filtering verdict.
Emails going to junk in Outlook are fixable once you stop guessing. A compauth failure or 5.7.515 bounce is an authentication job, a banned sending IP bounce is a delisting job, and CAT:BULK with a high BCL is a list and engagement job. Fix what the header points to, give it a few weeks of clean sending, and treat allow lists as a stopgap.


