Authentication passes, but Outlook still puts mail in Junk
When SPF, DKIM and DMARC all pass and Outlook still files your mail in Junk, the problem usually isn't authentication any more. Authentication answers "is this really from you?" Microsoft's filters then ask a second question: "do recipients want this?" Reputation, content, engagement, complaints and the recipient organization's own settings all feed that answer, and the message headers show which one tipped it.
So the way to stop emails going to Junk in Outlook starts with the recipient's copy of the headers, not with another DNS change. Tightening your DMARC policy won't move mail out of Junk. It can stop other people sending as your domain, but it doesn't tell a filter that your own mail is wanted.
First, rule out Microsoft's requirements
Microsoft has its own sender requirements for consumer Outlook.com mailboxes and its own anti-spoofing checks in Microsoft 365. If those aren't met, you're looking at a different problem, and Microsoft and Outlook authentication rules covers it. This page assumes they're met and picks up from there.
Get the headers from the recipient's side
Send a test message to an Outlook.com or Microsoft 365 mailbox you control, then open the message headers in that mailbox. The copy in your own Sent folder won't do: it was never filtered, so it carries none of the receiver's verdict. If you need to pass the headers to a colleague or a vendor, Is it safe to share email headers? explains what to redact and what to keep.
A simplified set of the lines that matter looks like this:
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
X-Forefront-Antispam-Report: CIP:203.0.113.25;...;SCL:5;...;CAT:SPM;...
X-Microsoft-Antispam: BCL:0;...
Check authentication properly
In Authentication-Results, confirm three things:
spf=pass,dkim=passanddmarc=passare all there.- The domains line up with your From domain.
header.fromis the domain your recipients see;smtp.mailfromis the envelope sender SPF checked;header.dis the domain that signed with DKIM. DMARC needs at least one of SPF or DKIM to pass for a domain aligned withheader.from. Envelope From vs Header From and Identifier alignment for SPF and DKIM explain alignment. compauth=pass. That's Microsoft's composite authentication result.
If something fails here, this isn't the right page. Go to Mail started failing after we published DMARC if mail started failing after a DMARC change, Third-party mail fails alignment if a third-party sender fails alignment, or DKIM signature not found if the DKIM record can't be found.
A compauth=fail with reason=001 means implicit authentication failed: the domain had no authentication records, or only weak ones, such as SPF ending in ~all or ?all, or a DMARC policy of p=none. A compauth failure doesn't block a message by itself. Microsoft weighs it with the other signals before deciding.
Read the verdict in the anti-spam headers
Once authentication is clean, the anti-spam headers tell you what actually happened.
CAT: in X-Forefront-Antispam-Report. Start here. It names the filter that acted on the message. Common values:
CAT: value |
What filtered the message |
|---|---|
SPM |
Spam |
HSPM |
High-confidence spam |
BULK |
Bulk mail |
PHSH |
Phishing |
SPOOF |
Spoofing |
SCL: (spam confidence level). It runs from -1 or 0 to 9. A value of -1 usually means spam filtering was skipped, for example because the recipient's organization allowed the sender or a mail-flow rule bypassed filtering. A value of 5 or higher generally goes with a spam verdict, and 9 is often seen on high-confidence spam. In Microsoft's cloud filtering, though, SCL no longer decides the verdict on its own. Don't treat a single SCL number as the cause. Read CAT: for what actually happened.
BCL (bulk complaint level) in X-Microsoft-Antispam. It runs from 0 to 9. A value of 0 means the message wasn't seen as coming from a bulk sender. Higher numbers mean the sender's bulk mail draws more complaints. Each Microsoft 365 organization picks the BCL level at which bulk mail gets filtered. The default anti-spam policy acts at 7 and above, and stricter preset policies act at 6 or 5.
Use the verdict to choose your next step:
SPMorHSPMwith authentication passing: look at reputation, content and complaints (the next three sections).BULK, or a highBCL: complaint signals are the main lever.- Only one recipient organization affected: their own policy is the likely cause (see the last troubleshooting section).
Reputation: the domain and IP behind the mail
Authentication ties each message to your domain, so once it passes, your domain's history counts for more, not less. A brand-new domain, a sudden jump in volume, a shared sending IP with a poor history or a recent burst of bounces can all push authenticated mail into Junk.
- Warm up new domains and new sending sources gradually. Start with recipients who expect your mail and raise volume step by step. No provider publishes a schedule, so watch results rather than following a fixed plan. Using a separate domain for outreach email covers a separate outreach domain, and How many emails can you send per day? covers daily limits and thresholds.
- Keep volume steady. A quiet domain that suddenly sends a large campaign looks different from one that sends a similar amount every week.
- Watch bounces. A rise in bounces usually means old or bad addresses are on the list.
- Check your IP-level data where you're eligible. Microsoft runs sender-data and complaint-feedback programs for senders to consumer Outlook.com mailboxes. They show how your sending IPs look from Microsoft's side.
IP and domain reputation explains IP and domain reputation in more depth.
Content and engagement
Your From domain isn't the only domain in a message. Filters look at all of them.
- Link and tracking domains. A link or click-tracking domain with a poor reputation, or one that has nothing to do with your brand, can pull a message down even when authentication passes. Check every domain in the message, including the ones your sending platform adds for tracking.
- Mismatched identities. A display name, From domain, Reply-To address and link domains that point to unrelated brands look like phishing. Keep them consistent and recognizably yours.
- Engagement. Mail that recipients ignore, delete unread or never reply to looks unwanted over time. Send to people who want the mail, and send less often to segments that rarely act on it. Email list hygiene: when to re-engage or suppress inactive and unengaged subscribers covers re-engaging and suppressing inactive and unengaged subscribers.
- Format basics. Include a plain-text part, a working unsubscribe link for marketing mail and a real reply address that someone reads.
This isn't about avoiding "spam words" or hiding content from filters. Fix the reason the mail looks unwanted instead.
Complaint signals
When recipients click "Junk" or "Report spam", that feedback affects how your later mail is filed. On bulk mail, a high BCL is the visible sign of complaint-driven filtering.
- Make leaving easier than complaining. A clear unsubscribe link that works in one step gives people an alternative to the spam button.
- Honor unsubscribes quickly. Someone who unsubscribed and still gets mail is likely to report the next one.
- Don't mail people who didn't ask. Purchased or scraped lists generate complaints whatever your authentication says.
What is a spam complaint rate? explains how complaint rates are measured and how to lower yours.
A Microsoft 365 organization can also send promotional bulk mail that's below its bulk threshold to a separate Promotions folder. That's a bulk verdict, not a spam verdict. If your newsletter lands there, the mail was classified as promotional bulk rather than judged harmful.
When only one company's Outlook junks your mail
If one company junks or quarantines your mail and everyone else receives it normally, their tenant's anti-spam policy is the likely cause. Your DNS can't override it. Their Microsoft 365 admin can review the message, add an allow rule if the mail is wanted, or report it to Microsoft as a false positive.
Asking a recipient to add you to their safe senders list can help that one mailbox. It doesn't fix a reputation or complaint problem, so use it as a stopgap, not the fix.
For consumer Outlook.com mailboxes, there's no tenant admin to ask. Microsoft's sender support is the route for having a specific filtering decision looked at, and there's no set response time.
If the mail goes to Microsoft 365 business mailboxes and the issue is in your own tenant's setup, DMARC for Microsoft 365 and Microsoft 365 or Google Workspace setup issues cover the configuration side.
What DMARC reports can and can't show here
DMARC aggregate reports show whether your mail passed SPF, DKIM and DMARC at each receiver that sends reports. They're the right tool for confirming that all your legitimate sources authenticate. They don't show whether a message landed in the inbox or in Junk, and they carry no complaint or engagement data.
So if your reports show your mail passing at Microsoft while recipients find it in Junk, the reports are doing their job: they've ruled authentication out. Aggregate (RUA) vs forensic (RUF) reports explains the report types, What visual DMARC analysis should show you covers what a visual view of them should show, and Authentication vs inbox placement explains why authentication and inbox placement are separate questions. Our product provides DMARC reporting and visual analysis; it doesn't measure inbox placement or complaints.
For the wider troubleshooting path across all mailbox providers, see Why legitimate email goes to spam.
Common mistakes
- Reading the headers from your own Sent folder. They don't contain the receiver's verdict.
- Stopping at
dmarc=pass. Check that the domains are aligned with your From domain too. - Treating every Junk placement as a DNS problem. Once authentication passes, DNS changes rarely help.
- Ignoring link and tracking domains. They're part of the message's reputation.
- Relying on safe-sender requests. They help one mailbox, not your reputation.
- Confusing bulk with spam. A bulk or promotional verdict is a different signal from a spam verdict.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
SPF, DKIM and DMARC pass. Why is my mail still in Junk?
Authentication proves the mail is from you. Outlook then judges reputation, content, engagement and complaints separately, and any of those can send authenticated mail to Junk.
What does SCL 9 mean?
It's usually seen on mail judged high-confidence spam. In Microsoft's cloud filtering, SCL doesn't decide the verdict on its own, so check CAT: for what actually happened.
What is BCL?
The bulk complaint level, from 0 to 9. A higher number means the sender's bulk mail draws more complaints.
What does compauth=fail reason=001 mean?
Microsoft couldn't confirm the sender through implicit authentication, usually because the domain has no authentication records or only weak ones, such as SPF ending in ~all or ?all, or a DMARC policy of p=none.
Can links in my email send it to Junk?
Yes. A link or tracking domain with a poor reputation can, even when authentication passes.
How do I stop emails going to Junk in Outlook 365 as an admin?
If the mail comes into your tenant and you trust the sender, review the message, add an allow rule if it's wanted, or report it to Microsoft as a false positive. If you're the sender, you can't change another company's filter. Their admin can.