Quantcast
Channel: Symantec Connect - Products - Discussions
Viewing all articles
Browse latest Browse all 986

Cannot connect to secondary MX record for Messagelabs domain

$
0
0
I need a solution

Hi,

We have a customer who is trying to connect to a company with hosted Messagelabs email security via Forcepoint servers using TLS.

We can connect to the primary MX record fine but the secondary MX record gives the following:-

Trying Server cluster2a.eu.messagelabs.com
SMTP test:
A connection attempt from rly25a.srv.mailcontrol.com:8882 to cluster2a.eu.messagelabs.com on the SMTP port returns:
220 server-12.tower-555.messagelabs.com ESMTP
------------------------------------------------------------
Traceroute reports that the path to cluster2a.eu.messagelabs.com from this cluster is:
Hop Round-trip time Router
1   local router
2 0.411 ms ae0.659.rtr02a.frcpt.net (85.115.52.131)
3 0.782 ms ae0-408.rtr01j.frcpt.net (85.115.48.11)
4 1.452 ms xe-2-2-0.er1.london-ld4.symsaas.net (195.66.225.41)
5 13.700 ms unknown-46-226-55.bb.symantec.net (46.226.55.2)
6 13.662 ms unknown-46-226-55.bb.symantec.net (46.226.55.1)
7 107.602 ms unknown-63-245-207.bb.symantec.net (63.245.207.138)
8 162.482 ms xe-5-3-7.bcr1.lga1.us.bb.symantec.net (63.245.207.109)
9 163.037 ms ae-1-0.bar1.phx2.us.bb.symantec.net (63.245.207.29)
10 162.705 ms messagelabs-2.bar1.phx2.us.bb.symantec.net (63.245.207.190)
11 162.590 ms mail555.messagelabs.com (216.82.251.230)
------------------------------------------------------------
Security setting verification:
Checking server security option 'Verify'....ERROR
 sayTo: unacceptable return code TEMPFAIL, 421, Service Temporarily Unavailable
------------------------------------------------------------
Overall connection status. Connection failed

Would you be able to help please?

Thanks,

Richard.

0

Viewing all articles
Browse latest Browse all 986

Trending Articles



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