Hi Symantec,
I am the administrator of a hosting company and one of our main mail server IP seems to be blocked by Symantec, and thus our users have been unable to send emails to many of their target email addresses that are hosted on MessageLabs servers.
Our IP is 202.150.222.139 and it always times out when attempting to connect to any clusterX.us.messagelabs.com server. It looks like it has been firewalled.
telnet cluster1.us.messagelabs.com 25
Trying 67.219.250.106...
Trying 67.219.247.48...
Trying 67.219.251.58...
Trying 67.219.246.96...
Trying 67.219.246.192...
Trying 67.219.246.202...
Trying 67.219.250.96...
Trying 67.219.251.48...
Trying 67.219.250.202...
Trying 67.219.246.106...
Trying 67.219.250.192...
Trying 67.219.247.58...
telnet: Unable to connect to remote host: Connection timed out
If I connect to the server using the secondary IP 202.150.222.140 it will connect successfully, thus it is not a routing problem.
telnet -b 202.150.222.140 cluster1.us.messagelabs.com 25
Trying 67.219.250.192...
Connected to mail340.messagelabs.com.
Escape character is '^]'.
220 server-16.tower-340.messagelabs.com ESMTP
The interesting thing that we have noted is that connecting to some EU servers clusterX.eu.messagelabs.com using the IP in question is perfectly fine.
telnet -b 202.150.222.139 cluster4.eu.messagelabs.com 25
Trying 46.226.52.100...
Connected to mail264.messagelabs.com.
Escape character is '^]'.
220 server-12.tower-264.messagelabs.com ESMTP
I have checked the IP on http://ipremoval.sms.symantec.com/ and it is clean, thus there is no option to request for an investigation.
While we can use the .140 IP as the sending IP temporarily, we would like to be able to use the primary IP 202.150.222.139 going forward.
Please assist where possible.
Many thanks in advance.
Roy Lee
ConceptLane Pte Ltd