How to Fix Office 365 Marking Company Emails as Spam (SCL 5)
Question details
Legitimate outbound company emails are being classified as spam by Office 365 Exchange Online, receiving a Spam Confidence Level (SCL) of 5 despite proper domain authentication.
- Product
- Office 365 (Exchange Online)
- Device & OS
- not provided
- Scenario
- Sending regular company emails to Office 365 recipients using an HTML signature containing links and images.
- Observed behavior
- The emails are routed to the recipients' Junk folders with an SCL 5 score, even though SPF, DKIM, and DMARC configurations are verified and correct.
Verify your domain's SPF, DKIM, and DMARC records using an online DNS validation tool to rule out basic email authentication failures before troubleshooting backend content filters.
Identify and Isolate Signature Triggers
HTML signatures with specific image hosting platforms or tracked URLs can trigger the Office 365 spam filter. Test with a plain-text signature to isolate the issue.
Even with perfect DNS authentication, the content of your email heavily influences deliverability. Exchange Online often flags messages based on blacklisted URLs or suspicious image hosting domains within HTML signatures.
In your email client, temporarily disable your HTML signature or switch to a completely plain-text signature without any links or images.
Send a new test email from your corporate account to an external Office 365 test inbox.
Open the received email in the test inbox, view the message headers, and look for the 'X-MS-Exchange-Organization-SCL' value. If the score drops to -1 or 1, the previous signature is the culprit.
Gradually add links and images back to your signature one by one, sending test emails each time, to identify exactly which element triggers the SCL 5 spam classification.
Use the Microsoft Anti-Spam Delist Portal
If you are sending from shared IP addresses (like Google Workspace) that have been flagged by Microsoft, you must request a manual delisting.
Escalate to Microsoft Backend Support
If delisting fails and removing signatures does not solve the issue, the domain may be caught in a strict backend filtering rule that requires administrator intervention.
Try WPS Office for Your Daily Document Needs
While resolving email delivery and Exchange filtering issues requires Microsoft administrator support, you can switch to WPS Office for a hassle-free, lightweight, and cost-effective solution for all your document processing tasks. It offers full compatibility with Microsoft formats without the complex backend configurations.
Frequently Asked Questions
What does SCL 5 mean in Office 365 message headers?
SCL stands for Spam Confidence Level. A score of 5 or 6 indicates that Exchange Online's filtering algorithms consider the email to be spam. Emails with this score are typically routed directly to the recipient's Junk Email folder.
Why are my emails marked as spam if SPF, DKIM, and DMARC all pass?
Passing email authentication verifies your identity, but it is only one part of deliverability. Office 365 also scans the actual content of the email. HTML signatures containing certain tracked URLs, shared blacklisted IP ranges, or suspicious image hosting can trigger the spam filter regardless of healthy DNS records.
How can I check the SCL score of an email I sent?
You need the recipient to view the message headers of the email you sent (often found by viewing message properties or 'View Source' in their email client). Look for the 'X-MS-Exchange-Organization-SCL' header to see the assigned spam score.
Can using a shared email provider affect my deliverability to Office 365?
Yes. If you use a shared email provider like Google Workspace or a third-party marketing platform, your emails might be routed through IP addresses shared with other organizations. If those IPs end up on a Microsoft blocklist due to someone else's behavior, your legitimate emails may also be penalized.
