Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 3660

400 4.4.7 Message delayed and 441 4.4.1 Error encountered while communicating with primary target IP address

$
0
0

Hi,

After shutting down the old Exchange server 2010 (Internal IP 115.135.55.10) in my data center, now I cannot send email to one of the important recipients in my group of companies:

Generating server: PRDEX24-VM.domain.com
Receiving server: [115.135.55.229] (115.135.55.229)
Banking@ParentCo.com
Remote Server at [115.135.55.229] (115.135.55.229) returned '400 4.4.7 Message delayed'
20/06/2018 8:45:40 PM - Remote Server at [115.135.55.229] (115.135.55.229) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." 
Attempted failover to alternate host, but that did not succeed. 
Either there are no alternate hosts, or delivery failed to all alternate hosts. 
The last endpoint attempted was 115.135.55.229:25'


The above is the NDR that I got when my customer and also myself from free webmail sending email to Banking@ParentCo.com.

PRDEX02-VM.domain.com is the existing Exchange Server 2013 where both domain.com and ParentCo.com are listed as the Authoritative Accepted email domain.

Usually, the email that is delivered to Banking@ParentCo.com is delivered to another Application server (Mainframe with the IP 115.135.55.229) through the Exchange server 2013.

How to fix the issue with the NDR above from external sender?


/* Server Support Specialist */


Viewing all articles
Browse latest Browse all 3660

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>