Incoming mail is working must out going mail is getting stuck in the queue
LED=441 4.4.1 Error Encountered while communicating with primary target IP address. Failed to connect. Winsock Error code 10061. Win32
error code 10061 attempted to failover to alternate host.
Exchange 2013 /windows 2012 server - just done a migration and changed the receive connect to the new exchange 2013 server
Mail is been pointed to a smart host - third party spam company's records
Will Szymkowski
From the Exchange 2013 server can you telnet to it and send a test email?
Will.
Rob Wesley
I'd check windows server firewall (turn off for testing), exchange services (all started?), smart host authentication (if the smart host requires it), perhaps verify with these sites and tools:
I've requested that this question be closed as follows:
Accepted answer: 0 points for Deepin's comment #a40837926
for the following reason:
Resolve was resolved by myself
Will Szymkowski
Please accept the below comment as the solution as NAT-ing has been stated already in my first comment.
NAT-ing is the terminology for what you have done for correcting your issue.
Will Szymkowski2015-06-18 at 14:33:59ID: 40837791
How are you sending mail? Do you have a send connector pointing to a SMTP smart host? Do you have proper NAT-ing in place from your smart host to your Exchange 2013 server?