Email Security.cloud

hi we migrated to a new server with new IP's all with good reputation and NOT blacklisted anywhere, but yet all my clients trying to send emails that are handled by messagelabs.com gets a timeout message. even the ones that are in a conversation back and forth for a while.

one example:

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 6 args: /usr/sbin/exim -C /etc/exim_outgoing.conf -v -M 1cZxGa-00014g-6j
delivering 1cZxGa-00014g-6j
Connecting to cluster8.eu.messagelabs.com [85.158.140.211]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8.eu.messagelabs.com [85.158.140.211] Connection timed out
Connecting to cluster8.eu.messagelabs.com [85.158.139.19]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8.eu.messagelabs.com [85.158.139.19] Connection timed out
Connecting to cluster8.eu.messagelabs.com [85.158.140.195]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8.eu.messagelabs.com [85.158.140.195] Connection timed out
Connecting to cluster8.eu.messagelabs.com [85.158.139.51]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8.eu.messagelabs.com [85.158.139.51] Connection timed out
Connecting to cluster8.eu.messagelabs.com [85.158.137.19]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8.eu.messagelabs.com [85.158.137.19] Connection timed out
Connecting to cluster8a.eu.messagelabs.com [216.82.251.230]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
  H=cluster8a.eu.messagelabs.com [216.82.251.230] Connection timed out
LOG: MAIN
  == ffredericks@slrconsulting.com R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out

our mail IP address is: 75.102.22.82

some did go through after a day or so, but now they still sitting in our mail queue for a few days now.

Hi Shane,

As per you private message to me. I can confirm that your IP 75.102.22.82 is not listed on our Blacklist and I have set your IP reputation to high across our infrastructure.

The Issue should now be resolved.

Please set this to resolved to prevent others adding to the Thread.

Kind regards

Kevin Brosnan

Tier 2 Senior Technical Support Engineer.

tx but still xcant connect, here is info from my erver tech:

Hello Shane,

do they by any chance have any traces of messages even attempting to reach their servers?

I see the cluster is not blocked for access from your side:
[root@server ~]# ping cluster1.eu.messagelabs.com.
PING cluster1.eu.messagelabs.com (85.158.136.67) 56(84) bytes of data.
64 bytes from mail207.messagelabs.com (85.158.136.67): icmp_seq=1 ttl=247 time=93.7 ms
64 bytes from mail207.messagelabs.com (85.158.136.67): icmp_seq=2 ttl=247 time=93.7 ms
64 bytes from mail207.messagelabs.com (85.158.136.67): icmp_seq=3 ttl=247 time=93.7 ms
^C
--- cluster1.eu.messagelabs.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2436ms
rtt min/avg/max/mdev = 93.709/93.739/93.772/0.354 ms


It doesn't allow send packets, though:
[root@server ~]# traceroute cluster1.eu.messagelabs.com.
traceroute to cluster1.eu.messagelabs.com. (85.158.136.67), 30 hops max, 60 byte packets
send: Operation not permitted

Each send attempt found in the log ends up the same:
[root@server ~]# grep 1caemO-0005hd-N9 /var/log/exim_mainlog
2017-02-06 10:36:09 1caemO-0005hd-N9 <= dmacfarlane@eco-pulse.co.za H=(DougPC) [105.227.186.8]:62000 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no A=dovecot_login:dmacfarlane@eco-pulse.co.za S=50810 id=004001d28054$115ab090$341011b0$@eco-pulse.co.za T="RE: Update: Swazi Border Patrol Road" for Prashika.Reddy@rhdhv.com
2017-02-06 10:36:13 cwd=/var/spool/MailScanner/incoming 5 args: /usr/sbin/exim -C /etc/exim_outgoing.conf -Mc 1caemO-0005hd-N9
2017-02-06 10:36:13 1caemO-0005hd-N9 SMTP connection outbound 1486370173 1caemO-0005hd-N9 eco-pulse.co.za prashika.reddy@rhdhv.com
2017-02-06 10:37:16 1caemO-0005hd-N9 H=cluster1.eu.messagelabs.com [85.158.136.227] Connection timed out
2017-02-06 10:38:19 1caemO-0005hd-N9 H=cluster1.eu.messagelabs.com [85.158.136.67] Connection timed out
2017-02-06 10:39:22 1caemO-0005hd-N9 H=cluster1.eu.messagelabs.com [193.109.254.67] Connection timed out
2017-02-06 10:40:25 1caemO-0005hd-N9 H=cluster1.eu.messagelabs.com [195.245.230.83] Connection timed out
2017-02-06 10:41:28 1caemO-0005hd-N9 H=cluster1a.eu.messagelabs.com [216.82.251.230] Connection timed out
2017-02-06 10:41:28 1caemO-0005hd-N9 == prashika.reddy@rhdhv.com <Prashika.Reddy@rhdhv.com> R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out


With connection timed out.

If they would have any information on this, that would be great, as this doesn't explain what the exact error is.

Please advise.

Hi Shame,

Do you have any hardward of security systems that are restricting your outbound connection,

There should be no reason why you cannot trace or ping the cluster1.eu hostname

Using an external tool you can see below

Ping 85.158.136.67
[cluster1.eu.messagelabs.com]
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 115 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 115 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 114 ms
Round trip time to 85.158.136.67: 118 ms

TraceRoute from Network-Tools.com to 85.158.136.67 [cluster1.eu.messagelabs.com]

Trace complete

We have no issues with Cluster1.eu and I can confirm we have other clients currently using the infrastructure without issue,

This leads me to believe that your problems could be network related

Kind Regards

Richard Brittain
Tier2 Senior Technical Support Engineer,

thank u kindly, i apologise, it seems they moved my mail to IP 75.102.22.16

pls check this for me, then we should be done

thanks again!

Hi Shane,

As per your private message to me. I can confirm that your IP 75.102.22.16  is not listed on our Blacklist and I have set your IP reputation to high across our infrastructure.

The Issue should now be resolved.

Please set this to resolved to prevent others adding to the Thread.

Kind regards

Kevin Brosnan

Tier 2 Senior Technical Support Engineer.

thank u very much, emails are now goinyh through