Update: Starting November 2022, protection.microsoft.com URL does not work anymore. Please go to security.microsoft.com instead for the AntiSpam feature mentioned in this post.
We realize that many...
Updated Dec 08, 2023
Version 10.0
Blog Post
What am I missing in this scenario:
- Default remote domain * = Auto-forwarding disabled
- custom remote domain contoso.com = Auto-forwarding enabled
- outbound spam policy = doesn't matter (contoso.com can be forwarded to).
Am I wrong? I am seeing proof of this in real life, with the exception that outbound spam policy is set to "Automatic", which per this blog post translates to "Off". Seems like a remote domain with auto-forward enabled trumps everything, except a Transport Rule.
If everything I've said is correct to this point, then the next question is - is the only intent, for the forwarding control in the outbound spam policy, to pick up the slack for when customers don't know better to go and turn the default remote domain *'s Auto-Forward setting to Off/Disabled? And if the answer to this one is yes, wouldn't it have been easier to just blog post about Remote Domains and their importance?
Please correct all my misassumptions. And thanks in advance.