Ok so here we go. I am currently working on moving our organization to office365. We are currently running on prem exchange 2016 and office365 in the cloud. Sophos XG firewall is configured for transparent filtering between the two mailservers.
The problem I have is that there is a header in the emails when they come from office 365. This header is "X-MS-Exchange-Organization-AuthAs: Anonymous". It should be ' X-MS-Exchange-Organization-AuthAs: Internal ' when everything is working properly. I went through all the office365 receive connector and transport rules and everything. Couldnt find the problem. I saw many references that you cant have mail appliances in the way, so i made a rule so that the traffic would bypass the SMTP and SMTPS checks. Lo and behold everything works. So 100% sophos XG is the problem.
I find it interesting that i cant find many other people with the same problem here. I found this post ( community.sophos.com/.../office365-deployment-best-practice ) that basically says we should run a long ass script that periodically updates the sophos XG with the correct IP address ranges for whitelisting. I dont really find this to be the most elegant solution, if i can even get it working.
So i am posting here. I had some ideas that i am going to try today, like making a parallel route from office365 to a different public IP address that then redirects to the mailserver for inbound messages and bypasses all the checks.
So this post is to document my progress towards a solution, and see if anyone else has this problem as well. Since we all now have to move to o365 as MS sunsets on prem exchange, I think its timely to have a good solution from the sophos side, as this will keep coming up again and again for people. I would go so far as to ask sophos to fix this problem on their end so we don't have to come up with crazy hacks. Office365 mail is going to become a bigger and bigger contender over the next few years till it is most likely the defacto standard like exchange was. Sophos should be able to deal with it in transparent mode by default.
This thread was automatically locked due to age.