Why Do My Emails Go to Junk in Outlook and Hotmail?

Outlook.com, Hotmail and Microsoft 365 send mail to the Junk folder when it fails authentication, comes from an IP or domain with a poor reputation, looks like bulk mail that recipients complain about, or contains links and content Microsoft's filters distrust. Unlike Gmail, Microsoft writes much of its verdict into the message headers, so the fastest way to find the cause is to send yourself a test, open the headers, and read what Microsoft decided.

Consumer Outlook.com (which includes hotmail.com and live.com) and business Microsoft 365 use related but different filtering. Both are covered below.

Consumer Outlook vs. Microsoft 365

Outlook.com and Hotmail are Microsoft's free consumer mailboxes. Filtering is driven by Microsoft's own reputation data on your IPs and domains, recipient complaints and authentication. You see your IP reputation through SNDS and complaints through JMRP.

Microsoft 365 (Exchange Online Protection, or EOP) protects business mailboxes. It uses Microsoft's global signals plus each organization's own policies. The recipient's admin controls the bulk mail threshold, allow and block lists, and whether bulk mail is junked at all. So a message can land in one company's inbox and another company's junk folder on the same day.

Read Microsoft's verdict in the headers

Send a test to a Microsoft 365 mailbox you control, open the full message source, and look for these headers. Our header analyzer will pull them out for you, and how to read an email header walks through the rest.

X-Forefront-Antispam-Report: CIP:203.0.113.7;CTRY:US;LANG:en;SCL:5;
 SRV:;IPV:NLI;SFV:SPM;H:mail.example.com;PTR:mail.example.com;CAT:SPM;...
X-Microsoft-Antispam: BCL:7;...

The fields that matter most:

If CAT:BULK and a high BCL: your mail is being classified as bulk that people complain about. In Microsoft's Standard preset policy, BCL 6 or higher goes to Junk by default. 0 means not bulk, 1 to 3 is bulk with few complaints, 4 to 7 mixed, 8 to 9 high.

If CAT:SPM or HSPM: the content filter and reputation signals rated it as spam. Look at your IP and domain reputation and your authentication.

If CAT:SPOOF: Microsoft doesn't believe the message really came from the From domain. Check the Authentication-Results header for SPF, DKIM, DMARC and compauth results.

Consumer Outlook.com mailboxes also add a header called X-Microsoft-Antispam-Mailbox-Delivery, and senders often read a dest:J value in it as "delivered to Junk." Microsoft doesn't document that header publicly, so treat it as a hint rather than a verdict.

The common causes, most likely first

1. Authentication gaps

Microsoft's postmaster policy requires that domains sending more than 5,000 messages a day to Outlook.com pass SPF and DKIM and publish DMARC of at least p=none, aligned with SPF or DKIM. Since May 2025, Microsoft has enforced these rules for high-volume senders, and non-compliant mail can be rejected with 550 5.7.515 rather than junked. Smaller senders aren't exempt from filtering either. Check everything with the SPF, DKIM and DMARC checker.

2. Poor IP reputation

Outlook.com leans heavily on IP reputation. Register your sending IPs with SNDS, Microsoft's free Smart Network Data Services. It shows each IP's filter results, complaint rate and spam trap hits. Red or yellow days line up with junking. If you're on a shared ESP pool, you inherit whatever the pool's reputation is.

3. Complaints and bulk classification

When recipients click "Report junk," it raises the BCL Microsoft assigns to mail like yours. Sign up for JMRP (the Junk Email Reporting Program, linked from SNDS) to get copies of those complaints, and suppress complainers. Microsoft doesn't publish a complaint rate threshold for Outlook.com.

4. Infrastructure basics

Microsoft's policies call for valid reverse DNS on sending IPs, no sending from dynamic IP space, honoring 5xx responses by not retrying, and staying under 500 simultaneous connections without prior arrangement. A missing PTR record alone can hurt.

5. Content and links

Links to domains with a poor reputation, URL shorteners, and image-only messages all count against you. Compare a plain text version of the same message: if it reaches the inbox and the full template doesn't, look at the links.

How to fix it, step by step

1. Send a test to a Microsoft 365 mailbox and read CAT, SFV, SCL and BCL in the headers.
2. Fix authentication. SPF for every sending service (watch the 10-lookup limit), DKIM signing on your own domain, and DMARC. The DMARC generator gives you a starting record.
3. Register in SNDS and JMRP. Check IP status daily while you work the problem.
4. Cut the complaint drivers. Stop mailing unengaged and old segments, make unsubscribing easy, and suppress JMRP complainers.
5. Check reverse DNS for every sending IP.
6. If you're blocked, not just junked, see why Outlook is blocking your email and how to get delisted by Microsoft.
7. Ask business recipients to help. In Microsoft 365, a user's "Not junk" report and Safe Senders entries apply to that mailbox, and the recipient's admin can submit false positives to Microsoft. You can't do this for them, but a key customer can.

How to confirm it's fixed

Repeat your header test and watch for SFV:NSPM and a lower BCL. Track SNDS daily status for a couple of weeks, and use seed testing to see placement across both Outlook.com and Microsoft 365 mailboxes. Engagement rates from Outlook and Hotmail addresses in your ESP reports should recover as placement does.

How to keep it from coming back

Keep SNDS and JMRP active, audit authentication whenever you add a sending tool, and segment by engagement so cold addresses don't drag down the mail your engaged readers want. If your problem is broader than Microsoft, start with why emails go to spam.

When to get help

If headers show clean authentication and SNDS is green but you're still junked, the cause is usually reputation or classification that takes experience to untangle. That's a good point to bring in help.

FAQ

Why does my email reach some Outlook users' inboxes but not others?

Microsoft 365 organizations set their own anti-spam policies and bulk thresholds, and individual users have their own Safe Senders and Blocked Senders lists. Consumer Outlook.com also weighs each recipient's own history with you.

Does asking recipients to add me to Safe Senders help?

For that recipient, yes. A Safe Senders match shows up as SFV:SFE and skips spam filtering for that mailbox. It doesn't help your reputation with anyone else.

Is SNDS enough to monitor Microsoft?

It covers IP reputation and complaints for Outlook.com consumer mailboxes. It won't show how individual Microsoft 365 organizations treat your mail, so pair it with header checks and seed tests.

Is there a Microsoft equivalent of Google Postmaster Tools?

SNDS and JMRP are the closest thing. Both are free, and both are IP-based, so you need to register every sending IP.