Email Security.cloud

Hello

I am also having aconnection problem from my main server IP 88.202.228.72 (host name leia.tlanet.co.uk). Our reputation is very good and we don't send spam. I believe the block was added prior to us being assigned the IP by our ISP UK2.

Can you please unblock us from your network as this is now costing us business and 2 clients have left us in the last few days!

examples of problems;

[root@leia ~]# grep 1bUstM-0007yw-DL /var/log/exim_mainlog
2016-08-03 10:55:12 1bUstM-0007yw-DL <= jkilner@hamiltonbailey.co.uk H=(JohnKilner) [82.23.150.60]:51464 P=esmtpsa X=TLSv1:ECDHE-RSA-AES256-SHA:256 CV=no A=dovecot_login:jkilner@hamiltonbailey.co.uk S=116152 id=009501d1ed6c$6e54ff10$4afefd30$@hamiltonbailey.co.uk T="RE: 09.08.16" for conferences@hotels-hull.co.uk
2016-08-03 10:55:12 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1bUstM-0007yw-DL
2016-08-03 10:55:12 1bUstM-0007yw-DL SMTP connection outbound 1470218112 1bUstM-0007yw-DL hamiltonbailey.co.uk conferences@hotels-hull.co.uk
2016-08-03 10:56:16 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.137.99] Connection timed out
2016-08-03 10:57:19 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.137.3] Connection timed out
2016-08-03 10:57:19 1bUstM-0007yw-DL == conferences@hotels-hull.co.uk R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out
2016-08-03 13:26:56 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.139.35] Connection timed out
2016-08-03 13:27:59 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.139.51] Connection timed out
2016-08-03 13:29:02 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.140.195] Connection timed out
2016-08-03 13:30:05 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.139.19] Connection timed out
2016-08-03 13:31:08 1bUstM-0007yw-DL H=cluster8.eu.messagelabs.com [85.158.140.211] Connection timed out
2016-08-03 13:32:11 1bUstM-0007yw-DL H=cluster8a.eu.messagelabs.com [216.82.251.230] Connection timed out
2016-08-03 13:32:11 1bUstM-0007yw-DL == conferences@hotels-hull.co.uk R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out
2016-08-03 19:20:04 1bUstM-0007yw-DL => conferences@hotels-hull.co.uk R=dkim_lookuphost T=dkim_remote_smtp H=cluster8.eu.messagelabs.com [85.158.139.19] X=TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256 CV=yes C="250 ok 1470248408 qp 15595 server-16.tower-178.messagelabs.com!1470248407!52173767!1"
2016-08-03 19:20:04 1bUstM-0007yw-DL Completed
[root@leia ~]#

Can you try a traceroute to any of those addresses please?  If your IP was blocked the symptoms should be different - you would get connected but then receive a 500 error,

Thanks for getting back to me;

[root@leia ~]# traceroute cluster8a.eu.messagelabs.com
traceroute to cluster8a.eu.messagelabs.com (85.158.139.103), 30 hops max, 60 byte packets
send: Operation not permitted
[root@leia ~]#

[root@leia ~]# traceroute server-16.tower-178.messagelabs.com
traceroute to server-16.tower-178.messagelabs.com (85.158.139.19), 30 hops max, 60 byte packets
send: Operation not permitted
[root@leia ~]#

Sorry iptables wasn;t letting traceroute work;

[root@leia ~]# traceroute server-16.tower-178.messagelabs.com
traceroute to server-16.tower-178.messagelabs.com (85.158.139.19), 30 hops max, 60 byte packets
 1  6d7b6503.lon.100tb.com (109.123.101.3)  0.400 ms  0.524 ms  0.693 ms
 2  83.170.70.233 (83.170.70.233)  0.850 ms 83.170.70.237 (83.170.70.237)  1.256 ms  1.320 ms
 3  lag-109.ear2.London2.Level3.net (212.187.139.153)  0.604 ms 83.170.70.130 (83.170.70.130)  0.941 ms lag-109.ear2.London2.Level3.net (212.187.139.153)  0.879 ms
 4  lag-109.ear2.London2.Level3.net (212.187.139.153)  1.338 ms  1.083 ms *
 5  * * MESSAGELABS.ear1.Amsterdam1.Level3.net (213.19.197.38)  7.206 ms
 6  unknown-46-226-55.bb.symantec.net (46.226.55.99)  7.532 ms MESSAGELABS.ear1.Amsterdam1.Level3.net (213.19.197.38)  7.364 ms  7.386 ms
 7  unknown-46-226-55.bb.symantec.net (46.226.55.99)  7.649 ms unknown-46-226-55.bb.symantec.net (46.226.55.191)  7.688 ms unknown-46-226-55.bb.symantec.net (46.226.55.189)  7.628 ms
 8  mail178.messagelabs.com (85.158.139.19)  7.573 ms unknown-46-226-55.bb.symantec.net (46.226.55.191)  7.832 ms mail178.messagelabs.com (85.158.139.19)  7.598 ms

[root@leia ~]# traceroute cluster8a.eu.messagelabs.com
traceroute to cluster8a.eu.messagelabs.com (85.158.139.103), 30 hops max, 60 byte packets
 1  6d7b6503.lon.100tb.com (109.123.101.3)  0.463 ms  0.583 ms  0.712 ms
 2  83.170.70.237 (83.170.70.237)  1.026 ms  0.863 ms  0.860 ms
 3  83.170.70.130 (83.170.70.130)  1.174 ms  1.232 ms  1.219 ms
 4  lag-109.ear2.London2.Level3.net (212.187.139.153)  0.738 ms  1.204 ms  0.957 ms
 5  MESSAGELABS.ear1.Amsterdam1.Level3.net (213.19.197.38)  7.265 ms ae-2-6.ear1.Amsterdam1.Level3.net (4.69.153.190)  7.587 ms  7.839 ms
 6  MESSAGELABS.ear1.Amsterdam1.Level3.net (213.19.197.38)  7.366 ms  7.347 ms  7.394 ms
 7  unknown-46-226-55.bb.symantec.net (46.226.55.189)  7.682 ms  7.743 ms  7.779 ms
 8  unknown-46-226-55.bb.symantec.net (46.226.55.191)  7.773 ms mail558.messagelabs.com (85.158.139.103)  7.490 ms unknown-46-226-55.bb.symantec.net (46.226.55.189)  7.733 ms

Hi Andy,

I have checked the reputation of the IP 88.202.228.72 on our infrastructure and confirm it is good and also that IP is not listed on our internal Black list.

Can you confirm if you are still having the issue when sending emails through us.

Kind regards

Kevin Brosnan