Odds are the folks looking at this probably don\u2019t do the bulk of the deployments for their companies. But in the odd chance that they are or have direct access to them, I\u2019m going to touch on a very important aspect of ExchangeDefender deployment: IP restrictions. First we\u2019ll start with a nice bright list of what the ranges are: <\/p>\n
\n\u00b7 65.99.255.0\/24<\/i><\/b> <\/p>\n
\u00b7 206.125.40.0\/24<\/i><\/b><\/p>\n<\/blockquote>\n
Now here\u2019s why you need to first off add them for your client\u2019s mail flow. Remember that in order for us to deliver mail on behalf of the original sender you have accept mail anonymously. This is very easy to do (it\u2019s just the next tab on the receive connector GUI. The downside to allowing anonymous delivery WITHOUT the restrictions is that you\u2019re one step away from being an \u201cOpen Relay\u201d. If you\u2019re an open relay, that will surely get your connection blacklisted on RBLs, it may get your access to our network revoked for a period of time based on the severity of the outbreak. So the cons of not setting these correctly are pretty huge: <\/p>\n
\n\u00b7 Interrupted\/Inconsistent inbound mail flow<\/i><\/b> <\/p>\n
\u00b7 Outbound mail flow restrictions<\/i><\/b><\/p>\n<\/blockquote>\n