Emails Going to Spam in Outlook But Not Gmail: Why

You send the same message to two people. It reaches the Gmail inbox and lands in the Outlook Junk folder. Nothing is broken — the two providers weigh spam signals differently, and one of your weak spots matters more to Microsoft than it does to Google. If you have wondered why do my emails go to spam in Outlook but not Gmail, the cause is almost always sender-side, and the fix is specific.

This guide gives the short answer first, then the exact Microsoft headers that name the signal that tripped, a side-by-side of how the two filters differ, and what to try when the mail keeps landing in Junk. Every Microsoft figure here is checked against Microsoft's own documentation.

The short answer: two filters, two priorities#

Microsoft's filter leans hard on the reputation of the sending IP address and on a bulk complaint level (BCL) score — a measure of how much a bulk sender's mail draws complaints. Google's filter leans more on domain reputation and on whether recipients actually engage with your mail. A sender who looks fine to Google can still trip Microsoft's IP or bulk signals.

That asymmetry explains the split. If you send from a new or shared IP with little history, Gmail may accept you on the strength of your domain while Outlook, with no IP reputation to trust, routes you to Junk. If your list generates complaints, Microsoft's BCL climbs and junks the mail before Gmail's domain-level view catches up.

There is also a hard authentication rule underneath all of this. Both providers now require SPF, DKIM, and DMARC once you send at volume, and Microsoft states its threshold and enforcement date plainly. Missing authentication is the single most common reason mail is junked at Outlook while an older, trusted Gmail relationship still lets it through.

Before you start: what you'll need#

Diagnosing this is a matter of reading evidence, not guessing. Gather these first so you can tell an IP-reputation problem from an authentication problem — they have different fixes.

• The full internet headers of one message that landed in Outlook's Junk folder — not the body, the headers.
• Access to your sending domain's DNS, so you can check and fix SPF, DKIM, and DMARC records.
• A Microsoft SNDS (Smart Network Data Services) account and enrolment in JMRP, the Junk Mail Reporting Program, for the IP you send from.
• A Google Postmaster Tools account for the same domain, to compare domain reputation and spam rate.
• Your ESP's complaint-rate and bounce dashboards, if you send through a provider.

How to diagnose it, step by step#

Work in order. The header tells you which signal Microsoft acted on, and the postmaster tools tell you why.

1. 1

   Open the message's full headers

   In the junked message, open the internet headers (the message-source view in Outlook on the web, or File > Properties in classic Outlook). Mail filtered by Microsoft carries an X-Forefront-Antispam-Report header packed with diagnostic fields.

2. 2

   Read the X-Forefront-Antispam-Report fields

   Find SFV, CAT, and SCL. SFV:SPM means spam filtering marked it as spam; SRV:BULK means it was flagged by the BCL threshold; CAT names the category applied. The bulk complaint level itself appears as a BCL value in the neighbouring X-Microsoft-Antispam header.

3. 3

   Check the authentication results

   In the Authentication-Results header, read spf, dkim, dmarc, and compauth. A compauth=fail or a dmarc=fail points at an authentication or alignment problem, not IP reputation — fix that first, because it is the cheapest and fastest to correct.

4. 4

   Look up the sending IP in SNDS

   Register the IP with Smart Network Data Services. SNDS reports Microsoft's complaint data and filter status per IP — the exact reputation Outlook is judging you on, and that Gmail never sees.

5. 5

   Compare with Google Postmaster Tools

   Read domain reputation and spam rate for the same domain. If Google shows high domain reputation and a low spam rate while Outlook junks the mail, the problem is Microsoft-specific: IP reputation or BCL, not your content.

6. 6

   Decide which signal tripped

   Authentication failure hits both providers, so it rarely explains an Outlook-only problem. An Outlook-only junking with clean auth points at IP reputation or a rising BCL — a bulk or complaint problem Microsoft weighs more heavily than Google.

The Outlook headers worth reading#

These fields tell you, in Microsoft's own words, what happened to the message. If the raw text is hard to scan, paste the header block into Microsoft's Message Header Analyzer, which parses it into a readable table.

Microsoft junk filter vs Gmail spam filter#

Both filters want the same outcome — wanted mail in, unwanted mail out — but they read different signals to get there. That is why one relationship can be healthy while the other is not.

One caution about the header: the SCL (spam confidence level) does not decide placement for cloud mailboxes. Microsoft says to read CAT and the BCL instead, and SCL is used mainly in on-premises and hybrid Exchange. Do not chase a low SCL when you should be lowering the BCL.

Same message, two verdicts#

The illustration maps the split. The same email meets two filters: Microsoft grades it mostly on the sending IP's reputation and its bulk complaint level, while Google grades it mostly on domain reputation and engagement. Shift the weighting and the same message routes to Junk on one side and the inbox on the other.

What to do when it still goes to Junk#

If authentication is clean and the mail still lands in Outlook's Junk folder, you are looking at a reputation problem, and reputation is rebuilt with time and behaviour, not a single setting.

1. 1

   Warm the sending IP

   A new or cold IP has no reputation for Microsoft to trust. Ramp volume gradually and keep it steady; sudden spikes read as spam-like and can set you back.

2. 2

   Reduce the complaint rate

   Every complaint pushes the BCL up. Mail only people who opted in, prune unengaged addresses, and make one-click unsubscribe (RFC 8058) easy so recipients opt out instead of reporting spam.

3. 3

   Enrol in JMRP and act on it

   The Junk Mail Reporting Program feeds you the complaints Outlook.com recipients file. Suppress those addresses immediately — repeat sends to complainers are the fastest way to keep the BCL high.

4. 4

   Ask key recipients to add you to Safe Senders

   A sender on a recipient's Safe Senders list skips filtering, stamped SFV:SFE in the header. For a handful of important contacts, this is an immediate and reliable fix.

5. 5

   Separate mail streams by subdomain

   Send newsletters and transactional mail from different subdomains, so a marketing complaint problem does not drag down the reputation your receipts and password resets depend on.

Where AI Emaily fits — and where it doesn't#

A straight answer, because this is a sender-side problem and AI Emaily sits on the other side of it. AI Emaily is an AI email client, not an email service provider, a bulk-sending platform, or a deliverability tester. It will not change your sending IP's reputation, lower your BCL, or move your mail out of someone else's Junk folder. That work belongs to the tools above — SNDS, JMRP, Google Postmaster Tools, and your ESP.

Where it fits is the mirror image. When you are the recipient and legitimate mail keeps landing in your own Outlook Junk folder while Gmail files it fine, AI Emaily re-triages inbound mail consistently across Gmail, Outlook, and IMAP in one place, with approve-before-file control and an audit trail, and its spam protection flags likely phishing before you see it. We build AI Emaily. That is the part it does; the deliverability work above it does not.