Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 4813 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Office 365 mail protection

Berlioz42300

Hi all,

 

After deploy the XG firewall i can't add the followind domain on exception for the reverse proxy mail :

*.mail.protection.outlook.com

*.protection.outlook.com

 

I don't want add manually all the scopes IP of microsoft protection. Do you have a solution for add this domain with * on exeception because with the RDNS check i don't receive mail from O365 and hotmail.

 

Thanks for your help.

Regards.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to dja

    Yes i'm sure, if you use rDNS check Strict, all O365, hotmail and live mail are blocked and its normally.

     

    If you send an email by a domain on Office 365 (test.fr for this example), the IP who want send your email is : xxxx.mail.protection.outlook.com !

    Microsoft know this problem and palo alto are impacted too by this problem on reverse mail proxy.

    The only solutions is exclude all ip of microsoft protection (too many IP and /22 or /16...) or exclude a domain totally.

     

    The best solutions is exclude all domain xxxx.mail.protection.outlook.com but we need to wait an update for enter wildcard on exclusion MTA.

  • 0 in reply to Berlioz42300

    Can you show us the exception, which you try to deploy? 

    I can successful build a FQDN Wildcard Exception in V17.5 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    I'm not in 17.5 because it's a beta version, i'm in 17.1.3 MR3 (latest version)

    But it's a good news when the version is ready for release !

  • 0 in reply to Berlioz42300

    Feel free to test V17.5

    Some of our customers already deploy it on their productive systems without any issues. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Not for me for the moment, i prefer wait...the migration between v16 and v17 remind me bad memories...

Cookie Information Banner