Given that best practices are to block exchange forwarding, it would be excellent if Huntress could automatically remove these rules as they're detected - similar to the response when an account is breached.

The situation we run into frequently is with temporary contractors that setup their email to forward to a personal email - if we don't immediately remove that forward, we get tickets about their emails bouncing of the error generated when Block Exchange Forwarding is enabled but a forwarding destination is still configured.