Blog Post

Exchange Team Blog
2 MIN READ

New Reply-all Storm Protection Report, Settings UI, and Alert Policy

The_Exchange_Team's avatar
The_Exchange_Team
Icon for Microsoft rankMicrosoft
Apr 22, 2022
The Reply-all Storm Protection feature in Exchange Online helps protect your organization from unwanted and disruptive reply-all storms. Last year we updated the feature to give admins the ability to...
Updated Apr 23, 2022
Version 2.0
announcements
Exchange Online
transport
Arindam_Thokder's avatar
Arindam_Thokder
Icon for Microsoft rankMicrosoft
May 04, 2022

tonire - You mentioned it was working last week, so I guess it is related to the recent change that Kevin mentioned earlier and SenderRewritingEnabled is not the solution. Your routing is as following -

Internet -> third party mailgateway -> EXO -> mailbox forwarding -> third party mailgateway -> forwarded target mail system
In the above routing scenario, inbound SPF on EXO would always fail because the sender is internet but sending IP as far as EXO sees it is the mailgateway. To avoid the SPF failure, there is a feature called "Enhanced Filtering for Connectors in Exchange Online" which will help EXO to find the IP address of the actual sender and that would solve the Inbound SPF issue as well as SRS rewriting. I suggest you to configure "Enhanced Filtering for Connectors in Exchange Online". If it's already configured and you are still facing the issue, please open a support ticket.