Email Security.cloud

We cannot send email to our bank!  We keep getting the following error connect to cluster5.us.messagelabs.com[216.82.241.195]:25 connection timed out.

I have check the symantec blacklist and it says we do not have a negative reputation so we can not be investogated.  We need to be able to send email to our bank at pnc.com!

Our mail servers ip address is 24.154.65.53 and its domain is imail.fluentcpas.com please HELP!

Hi Justin,

I can now confirm that I have now reset the confidence of that IP accross all our towers.

This will fix the issue and you will no longer get issues sending emails from that IP to our customers.

Please set this thread as resolved to prevent other people adding to it.

Kind regards

Kevin Brosnan

Tier 2 Senior Technical Support Engineer

Hi Justin,

Just following up on this and wondered if you require any further information.

If not please can you set this thread as resolved to prevent others adding to it.

Kind regards

Kevin Brosnan
Tier 2 Senior Technical Support Engineer
CompTIA Security+ Certified

I"m the system admin for ATNI.NET, our email server is not blacklisted so I'm not sure why but outgoing emails to messagelabs.com are timing out, they are recieved just fine.

Jul 18 14:42:55 mail amavis[15495]: (15495-04) Checking: Fj4h_NLXAgLV MYNETS [127.0.0.1] <ivera@atni.net> -> <Beard-Christina@aramark.com>
Jul 18 14:42:55 mail amavis[15495]: (15495-04) Fj4h_NLXAgLV FWD from <ivera@atni.net> -> <Beard-Christina@aramark.com>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4BFEF20210E3
Jul 18 14:42:55 mail amavis[15495]: (15495-04) Passed CLEAN {RelayedOutbound}, MYNETS LOCAL [127.0.0.1]:47785 [96.61.128.254] <ivera@atni.net> -> <Beard-Christina@aramark.com>, Queue-ID: 112F120210E3, Message-ID: <009701d2ffd9$677c4830$3674d890$@atni.net>, mail_id: Fj4h_NLXAgLV, Hits: -3.998, size: 15124, queued_as: 4BFEF20210E3, dkim_sd=CCD20A06-63B9-11E6-AE3B-5DFA9C2E6DCD:atni.net, 312 ms

Jul 18 14:45:25 mail postfix/smtp[30284]: 4BFEF20210E3: to=<Beard-Christina@aramark.com>, relay=none, delay=150, delays=0.06/0/150/0, dsn=4.4.1, status=deferred (connect to cluster1.us.messagelabs.com[216.82.249.211]:25: Connection timed out)
Jul 18 14:53:16 mail postfix/smtp[6972]: 4BFEF20210E3: to=<Beard-Christina@aramark.com>, relay=none, delay=621, delays=471/0.02/150/0, dsn=4.4.1, status=deferred (connect to cluster1.us.messagelabs.com[216.82.242.44]:25: Connection timed out)

Any ideas would be wonderful

Michael

michael@atni.net

Hi Michael

Can you let me know your sending IP so I can check this?

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

We are having the same problems with emails being delayed for delivery through the messagelabs spam filter.  I have multiple domains that we send mails to customers that use your filter, and all are bouning back after 4 hour and stating they are delayed.  We have customers that are mad and thinking we are not responding to their mails, when we do but cannot get through your filter.  I have bounces and even trying to telnet to send mails does not work.  I have got to get this resolved and the only clients that have this problem with mail delivery are using your messagelabs product.  We use an inhouse Exchange 2013 server and I have been working with Exchange since 5.0 version.  NEED TO GET THIS RESOLVED.... 

Regards,

Chris Roberts

chrisroberts@industrialchem.com

Hi Chris

Can you please ket me know your IP so I can get this checked out?

Thanks

Ian Tiller

Tier 2 Senior Technical Support Engineer

Ian,

Our external IP address is 12.97.139.19 we do not use a smart host.  Thanks...

Thank you Ian.   The sending IP is 173.224.64.221

Appreciate your help!

Mihael

Hi Chris

I checked your IP and I cannot see any specific issues directly related to it.

You mentioned you had some bouncebacks, can you let me know what the bounces are as these may give a clue as to the problem.

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

Shire.com domain Delivery is delayed to these recipients or groups:

Diagnostic information for administrators:

Generating server: Onsite Exchange (Removed Name)
Receiving server: cluster2a.eu.messagelabs.com (216.82.251.230)
 

Remote Server at cluster2a.eu.messagelabs.com (216.82.251.230) returned '400 4.4.7 Message delayed'
7/13/2017 9:34:02 PM - Remote Server at cluster2a.eu.messagelabs.com (216.82.251.230) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "421 4.4.2 Connection dropped due to ConnectionReset." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 216.82.251.230:25'

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

barsol.com domain Delivery is delayed to these recipients or groups:

Diagnostic information for administrators:

Generating server: Onsite Exchange (Removed Name)
Receiving server: cluster6a.us.messagelabs.com (216.82.251.230)

Remote Server at cluster6a.us.messagelabs.com (216.82.251.230) returned '400 4.4.7 Message delayed'
7/13/2017 3:30:51 PM - Remote Server at cluster6a.us.messagelabs.com (216.82.251.230) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "421 4.4.2 Connection dropped due to ConnectionReset." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 216.82.251.230:25'

I have others but they all read the same as the 2 above.  Please let me know if you need anything else and thanks for your time and help.  

Regards,

Chris Roberts

Hi Chris

I've sent you a PM in regards to this issue,

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

Hi Chris

This is an intriguing one. Usually when someone is hitting the 'a clusters' (cluster6a.us.messagelabs.com for example) this usually means that the sending IP is being throttled to a point where it cannot connect to the correct MX record which in this case should be cluster6.us.messagelabs.com.

The other main cause for this issue is that the recipients have their MX records configured the wrong way around, however in your case neither of these appears to apply.

The only other time I've seen this is when the sending mail server was experiencing an issue with resolving DNS and wasnt able to resolve the MX records correcty. Can I ask if you have tried flushing DNS at all? I think at this point this would be helpful.

If not I think the next step is to ask one of the clients you are experiencing an issue mailing to open a support ticket so that we can investigate this in more detail.

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

Our email server is having the same issue sending to clients who use messagelabs.com -- they are delayed for hours which is causing major disruptions in business.  

Our server ip is:   216.196.177.194  We have been going around and around with this since June 2017. 

Hi Molls2008

I have rectified the issue with your IP.

Can you check and confirm its working as expected now.

If so can I ask you to mark this thread as resolved?

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

Hello there,

Thought I would jump on the back of this one please! I to am having issues with one of our mail servers sending to Messagelab servers, would someone mind having a quick look for me please?

The IP in question is 78.129.254.212

Many thanks,

Kev

Here is a copy of a log file if it helps:

Tue 2017-08-29 14:16:12: MX-record resolution of [customerMX] in progress
Tue 2017-08-29 14:16:12: *  P=020 D=CustomerMX TTL=(0) MX=[cluster5a.eu.messagelabs.com]
Tue 2017-08-29 14:16:12: *  P=010 D=CustomerMX TTL=(0) MX=[cluster5.eu.messagelabs.com]
Tue 2017-08-29 14:16:12: A-record resolution of [cluster5.eu.messagelabs.com] in progress
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [193.109.254.3]
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [85.158.138.179]
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [85.158.139.163]
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [195.245.230.51]
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [85.158.136.83]
Tue 2017-08-29 14:16:12: Host [cluster5.eu.messagelabs.com] resolved to [193.109.255.99]
Tue 2017-08-29 14:16:12: Attempting TCP connection to [193.109.254.3 : 25]
Tue 2017-08-29 14:16:33: Socket connection failed: Connection timed out
Tue 2017-08-29 14:16:33: Attempting TCP connection to [85.158.138.179 : 25]
Tue 2017-08-29 14:16:54: Socket connection failed: Connection timed out
Tue 2017-08-29 14:16:54: Attempting TCP connection to [85.158.139.163 : 25]
Tue 2017-08-29 14:17:15: Socket connection failed: Connection timed out
Tue 2017-08-29 14:17:15: Attempting TCP connection to [195.245.230.51 : 25]
Tue 2017-08-29 14:17:36: Socket connection failed: Connection timed out
Tue 2017-08-29 14:17:36: Attempting TCP connection to [85.158.136.83 : 25]
Tue 2017-08-29 14:17:57: Socket connection failed: Connection timed out
Tue 2017-08-29 14:17:57: Attempting TCP connection to [193.109.255.99 : 25]
Tue 2017-08-29 14:18:18: Socket connection failed: Connection timed out
Tue 2017-08-29 14:18:18: A-record resolution of [cluster5a.eu.messagelabs.com] in progress
Tue 2017-08-29 14:18:18: Host [cluster5a.eu.messagelabs.com] resolved to [85.158.139.103]
Tue 2017-08-29 14:18:18: Host [cluster5a.eu.messagelabs.com] resolved to [216.82.251.230]
Tue 2017-08-29 14:18:18: Attempting TCP connection to [85.158.139.103 : 25]
Tue 2017-08-29 14:18:39: Socket connection failed: Connection timed out
Tue 2017-08-29 14:18:39: Attempting TCP connection to [216.82.251.230 : 25]
Tue 2017-08-29 14:19:00: Socket connection failed: Connection timed out
Tue 2017-08-29 14:19:00: SMTP session terminated (Bytes in/out: 0/0)

Hi Kev

I've taken a look at your IP and have been able to clear the throttling thats in place on it.

As such mail should be flowing normally again now.

Can I ask you to check and confirm and if everything is ok to mark this thread as resolved?

Thank you

Ian Tiller

Tier 2 Senior Technical Support Engineer

Hi Ian,

Many thanks for looking at that for me, much appreciated!

I haven't had any complaints from people so far so it looks like all is well. If not I'll let you know!

Best regards,

Kev

Hi Ian,

We are also having the same issue for the last two weeks.  Our emails are sometimes delayes as much as 4-5days.  Our sending IP address is 50.235.103.167

Thanks,

John