We often get questions regarding mail forwarding in Exchange Online. As you already know, Exchange Online is a shared service. We must take care that users cannot take the service down by creating ma...
Updated Apr 30, 2021
Version 1.0
Blog Post
Just ran into this issue. I have a wildcard catchall address redirecting to a user (*@example.com -> user @example.com for all unknown *); that user setup a rule to redirect messages with tracking numbers to a shipping tracker, which failed because of the redirect limit. The redirect limit should be increased or Exchange should support catchall addresses natively without the transport rule hack, and the three workarounds are useless in this case: on-premises Exchange is out of the question, PowerShell forwarding doesn't allow conditions (only want to forward emails with tracking numbers), and PowerAutomate is crap.