Armitage318
asked on
DnsConnectionDelivery issue with Exchange 2013
Hi,
I am using Exchange 2013 on Windows Server 2012 R2.
I tried to send a message to 4 recipients (ALL in same external domain, eg. domain.com).
The error I got is:
"Remote Server at mail.domain.com (80.xx.yyy.zzz) returned '400 4.4.7 Message delayed'
04/03/2019 18:20:19 - Remote Server at mail.domain.com (80.xx.yyy.zzz) returned '451 4.4.0 Primary target IP address responded with: "421 4.4.1 Connection timed out." 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 80.xx.yyy.zzz:25'
Anyway, I tried manually with telnet (I mean: telnet domani.com 25) and it is reachable (I see banner of remote SMTP).
I also tried "retry" but without success (it seems they are stuck in "DnsConnectorDelivery").
How can I fix this?
thank you!
I am using Exchange 2013 on Windows Server 2012 R2.
I tried to send a message to 4 recipients (ALL in same external domain, eg. domain.com).
The error I got is:
"Remote Server at mail.domain.com (80.xx.yyy.zzz) returned '400 4.4.7 Message delayed'
04/03/2019 18:20:19 - Remote Server at mail.domain.com (80.xx.yyy.zzz) returned '451 4.4.0 Primary target IP address responded with: "421 4.4.1 Connection timed out." 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 80.xx.yyy.zzz:25'
Anyway, I tried manually with telnet (I mean: telnet domani.com 25) and it is reachable (I see banner of remote SMTP).
I also tried "retry" but without success (it seems they are stuck in "DnsConnectorDelivery").
How can I fix this?
thank you!
You are able to send emails to other external domains? If not, check if your exchange public IP got blacklisted
If yes, check from gmail if you can send test email to that specific external domain recipients
If yes, probably they have blocked your public IPs / domain, check with them
If yes, check from gmail if you can send test email to that specific external domain recipients
If yes, probably they have blocked your public IPs / domain, check with them
ASKER
Hi Senior IT System Engineer,
I have 3 send connector on my Exchange.
The one that matches domain.com is called "Internet", and basically send messages directly (without smarthost).
I would like to create a "workaround", and try sending messages to domain.com to a different smarthost on my network; with a different source IP address, I hope messages will be delivered.
Just one doubt: If I do this, will messages in current queue processed by new send connector?
Or will they still using the previouos one ("Internet")?
Thank you
I have 3 send connector on my Exchange.
The one that matches domain.com is called "Internet", and basically send messages directly (without smarthost).
I would like to create a "workaround", and try sending messages to domain.com to a different smarthost on my network; with a different source IP address, I hope messages will be delivered.
Just one doubt: If I do this, will messages in current queue processed by new send connector?
Or will they still using the previouos one ("Internet")?
Thank you
ASKER
HI Mahesh, I have no issue with other external domains.
Thank you
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Usually, it is the error type of the Send Connector. Can you please let us know what it is currently setup?