example-com.mail.protection.outlook.comfor the address in the Forward To field.
When using Xeams in the front, servers on Office 365 will see every message coming from your IP address, which
could kick in the rate limits on Microsoft's end and you could see the following error message in the
451 5.7.(500-699) Server Busy. Please try again later.
The following steps are copied from this page on Microsoft's site to add a connector, which resolves this issue.
Inbound filtering rules are improved when you let Xeams look at messages that are going out to users on the Internet. There are two ways to accomplish this:
This is the preferred method since it reduces an extra network hop and requires less configuration.