Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1010
  • Last Modified:

TLS Connect failed....I'm not going to try again

Hi,

I'm having a strange email issue.  Basically, my company can receive most external emails just fine, but
when emails are sent from one particular external domain, the emails get bounced back to the sender SLOOOWLY.
After several days, the sender will receive an email that says something like this:

TLS Connect failed.  connected to xyz.ab.de.fg
I'm not going to try again; this message has been in the queue too long.

The same emails are delivered properly to gmail accounts.

the MX records appear to be fine and I notice no other issues in the logs of our
firewall or exchange server (we're using Exchange 2003).

We thought this might be a TLS issue, but we are receiving TLS-encrypted emails from other domains, so I'm not sure that's the issue.

I've seen similar questions on experts-exchange, but without satisfactory resolution.

Any ideas as to what/where to test?
I'm not a sysadmin/exchange expert...it's just a job I inherited, so go easy!

Thanks!
0
pdanese
Asked:
pdanese
  • 3
  • 3
  • 2
2 Solutions
 
dpk_walCommented:
Although I am not an expert on exchange; writing this comment as it might help, I think either NDR or reverse DNS lookup can be the cause of the behavior observed.

Thank you.
0
 
pdaneseAuthor Commented:
Hi, thank you for the response.

I have a few questions, tho...what is NDR?

also, could you elaborate on reverse dns lookup being 'the cause'?

0
 
pdaneseAuthor Commented:
i just looked up NDR...that seems to be an error when the recipient doesn't exist.

that is not the case here.  the recipients *do* exist and they receive emails from most sources just fine.  but no one in our domain is capable of receiving emails from one specific external domain.

hope that helps clarify the issue.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
dpk_walCommented:
If you are using a firewall which does NAT for your email server and the MX record and the public IP of the firewall are different; the firewall normally sends all outbound traffic from the server using the puclic IP instead of MX record; in this case the domain which is doing reverse DNS lookup would not accept the emails from your domain. To overcome this problem we configure 1-1 NAT; and this ensures that all outbound traffic from server goes out with the same IP as the MX record IP.

As you clarified NDR is not the issue. If this is ruled out then I am not sure what else is the issue.

Thank you.
0
 
RobinHumanCommented:
This sounds like a TLS authentication issue on the recipient's side - I suggest that you contact them and advise them of this issue - could be the trust with them no longer exists.
0
 
pdaneseAuthor Commented:
suggestions didn't fix the problem but I wanted to distribute points to close the question.

Thanks to both for responding!
0
 
dpk_walCommented:
Thank you for the points.
0
 
RobinHumanCommented:
Thank you
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now