When i am sending mail outside from my domain then it is showing this error

Error encountered while communicating with primary target ip address “Failed to connect winsock error code 10061, Win32 error code 10061” Attempted failover to alternate host but did not succeed.

One last ting I noticed, in your final step to troubleshoot (love that your post have these), it shows your email was stuck in Queue for almost an hour before google finally sent it on, however it shows it sent it connecting via ESMTPS, and not standard SMTP…. from all my testing so far by default, unless you configure it otherwise it always send over standard SMTP (Port 25), does the comment you stated above apply to most external domain email recipient servers?

You stated the Following:

“Many email security servers/appliances or even hosted solutions will simply authenticate you based on your IP address rather than require other credentials.”

Now my domain (Zewwy.ca) points to my public IP address for my basic home network (which I have a NAT rule on my Modem to point to my Web Server, to host my website), this however is not the IP address which email will be coming from. I created a MX record and A record for mx.zewwy.ca for this (which I want email coming in and our from). Will external providers validate me based on my root domain IP? or my mx record?

For some reason when I put my info into mxtoolbox’s whois, it reported a differen’t MX then the mx record I created in my DNS providers portal… Would this be due to replication (cache)? I did check shortly after the change (AKAIK TTY can be up to 3 hours generally).

Thanks for all your contributions, They are really good specially when things don’t work, which tends to be the case more often than not.

I finally managed to setup my Exchange 2013 Server to play with from home (Separate Network, then my home network, and use a Palo Alto Firewall to create my Virtual Routers to separate my two internal and two external networks) Now as far as I know I configured everything correctly and my Exchange server and reach external web-sites and what not without issue. However when I attempt to send an email I see it stuck in the transport queue (Get-Queue), when I check my firewall I see the SMTP port 25 connections are allowed, and they all report the applicatino as incomplete, as if the connections are not allowed.

So using information from your other posts, I used the telnet trick to verify connectivity, and it seems from any computer in my networks (personal, or my test enviro) I can’t seem to connect to any of the external SMTP servers on port 25…

What am I missing, Do they require some form of Auth to work? TO me it doesn’t even seem to be the case as that would imply we’ve reached the application layer and my packets in my firewall would have said they are SMTP and no “incomplete” it’s like it’s being blocked at the 3rd layer (port). Do all external mail providers allow incoming SMTP email from anyone?

Any idea on what I may have missed would be greatly appreciated. I source your blogs on my blogs 🙂

Search for how to configure a relay connector for your version of Exchange.

We are using an internal mail client (on powerbuilder) which is connected to Outlook 2013. We send a mail from this mail client which then sends it through Outlook to sener. From last week, on 9 out of 10 mails (mostly to external IDs) the mails are not reaching the recipients and we are getting failure notice — The following recipient(s) cannot be reached:

Server error: ‘550 5.7.1 Unable to relay’

Pls help