Redirect delayed email through other node in cluster

[Tibor M]

Hi,

we facing problem that sometimes our customers blocking traffic from IP ranges based on geolocation. Mostly we see this in USA where they are paranoid and blocking everything including Europe for SMTP traffic. So we are unable to send them emails and we had to establish another ESA node on USA and manually forwarding email from exchange over send connector to USA based ESA node.

Does have ESA (1 cluster, 3 nodes) some feature (and if yes how it's called and hot to configure it?) which check sent email and if it's delayed (in our case 3 days) then it will try to send it automatically from next node in cluster and if it's delayed even there, try to send it from all other nodes, one by one?

We want to get rid of manual send connector configuration for targeting email domains each time our employees find our their emails are not delivered.

Thanks

[UdupiKrishna]

The straight forward answer is "no", though i know it's not the answer that you wish to hear. However there are ways to tackle this.

If the ESA(s) are able to reach each on port 25 you can setup something like this,

= If you are maintaining SMTP route configuration on a cluster level, create a machine level override on ESA(s) outside of US.

= Create an SMTP route on those ESA(s) pointing the recipient domain to the IP address of US ESA.

= Given you logically want these emails to be considered as "outgoing" add non US ESA IP addresses into the RELAYLIST sender group

This way emails that arrive on non US ESA will relay these emails to US ESA (using the SMTP route) and then US ESA will use MX records to deliver the email. 

Draw backs,

= Maintaining different SMTP route configuration on non-US ESA since they are no longer uniform.

= If you are using an SMA, you will see two copies of message tracking of the same email since they are processed twice.