96 votesGP admin commented
The bigger problem is /ews being available from OWA, forcing admins to either stand up a reverse proxy to block it or use user agent strings. It would still be helpful if support could share these user agent strings with customers
112 votes10 comments · Office 365 Security & Compliance » Spam & Phishing · Flag idea as inappropriate… · Admin →
When you have another service scanning in front of Office 365, the proper thing to do is disable the Office 365 scanning altogether and (optionally) respect the verdict from the prior system. Once you do that, even with the SPF header, the mails will not go to the users’ junk folders.GP admin commented
We’re using Mimecast as our 3rd party spam filter and every email received from the internet generates an SPF softfail. Could this feature please be researched?