51–60 of 140 posts
My work office365 mailbox is unusable. Normal mails ends up in spam or quarantine, or gets delivered with a very large delay.
This is another reason why we use a third party filter and dial the MS one way down.
The fact that Microsoft doesn't just whitelist their own domains speaks to their commitment to strict security measures and good engineering culture. Special cases aren't special enough to break the rules.
In other words: `*.notify.trafficmanager.net` is special-cased, and this has caused problems.
The fact that Microsoft doesn't just whitelist their own domains speaks to their commitment to strict security measures and good engineering culture. Special cases aren't special enough to break the rules.
My guess here is that some junk folder routing is on client side, or the user flagged junky email from the same infrastructure as junk. Or, O365 tweaked some settings to address the issues with spammers using Outlook infrastructure that bypasses spam controls.
Earlier quoted context omitted.
>speaks to their commitment to strict security measures and good engineering culture Does it really or does it just mean that nobody cared enough to do it for whatever reason?
I'm sure the Azure people are aware and annoyed. I appreciate that the security people are holding the line.
It would seem they actually do whitelist some of their own stuff - specifically those weird "Microsoft Viva" emails that Outlook users get. A year or two ago, I did get Outlook to classify those emails as "Junk" automatically, by repeatedly reporting them - but then something changed, and after that they never were marked as "junk" again - no matter how often I do report them.
The fact that Microsoft doesn't just whitelist their own domains speaks to their commitment to strict security measures and good engineering culture. Special cases aren't special enough to break the rules.