Forum Discussion
Anti-spam protection policy (scan2mail) false positives
Problem appears to be slackening.
Submission verdicts all come back "Not spam. Should not have been blocked."
Nothing relevant in Service Health indicating there was a problem.
Like ExMSW4319 above, we have a similar looking report:
Its rather galling to have support tell us that nothing has changed. Clearly something has changed. Fortunately on this post, there has been communication thru @MathieuVandenHautte that there is an issue with emails being misidentified. I even saw a post that said someone at Microsoft acknowledged that spammers had found a way to circumvent some of the spam filtering and this was the cause in the uptick. Its unfortunate that Microsoft can't admit this is the case on their health status notifications. Our company has tech savy bosses who know tro look for these health alerts. When these issues are properly identified and noted in posts, the burden falls on our staff for explaining whats happening. Our staff gets hung out to dry because MS refuses to acknowledge the issue. MS needs to know this approach to minimizing reported outages is not popular and a terrible way to treat their extended support family!
- EX530821: Exchange Online Service Health Notification
Some users' email messages are unexpectedly delivered to the Junk Email folder or quarantined in Exchange Online
Final status: We’ve determined that a recent update to optimize the detection proficiency of potential spam prior to delivery caused some legitimate messages to be incorrectly flagged and delivered to the Junk Email folder or quarantined in Exchange Online. We’ve published an update to our detection systems to address this issue and confirmed via telemetry that that the issue is resolved.
