Anti-spam inbound policy working differently without intervention

Copper Contributor

Last month, I ran a message trace to see what emails were failing to be delivered due to the spam policy. I had a suspicion that some important emails were not being delivered. After looking at the report, indeed some emails that I had previously received from senders were now failing to be delivered. I have never made changes to the anti-spam inbound policy. I've only added entries to the allowed/blocked senders/domains.

 

Has Microsoft changed something within the past few months or so that affected the spam priority behavior or anything else? I find it very odd that emails that I've received in the past are now randomly failing to be delivered. Now, I have had to send all spam-detected emails to the Junk email box instead of automatically deleting them, which is not what I wish to do.

5 Replies

@JonasBack This is highly possible. Thank you. I have made some changes, accordingly, and will monitor. 🙂 I'll report back if something doesn't appear to be working as expected.

I don't believe this is a DMARC issue. For example, I received two emails from the same Verizon email address. One was filtered as spam and the other one was delivered normally. This is happening with other email addresses, and seems to be happening at random. This has me baffled, but I would like it fixed. What do you suggest?

Did you find the cause of this issue? We're experiencing a similar problem, and we haven't made any changes to the anti-spam inbound policy either

 

@UserID144294 No I haven't. However, I turned off the Preset Security Policies in Threat Policies and am managing this on my own. I don't have much faith in that right now. So far I haven't had any more issues. Maybe that was part of it.