Email Security.cloud

 View Only
  • 1.  Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Feb 01, 2016 05:21 PM

    I run a VDS server and recently I moved hosts from HostGator to this new server, but several of my clients started having problems delivering email to their own customers. My email queue states only messagelabs as the cause of the undelivered messages. I am having a great deal of trouble with this since my customers can have their email delivered. I have searched on several sites but seems like there's no way to delist an IP address other than being here and having everything setup on my DNS settings. I have created SPF and DKIM correctly and even used Googles DKIM settings for my server, is there a way to finding out what could be causing the blocking by messagelabs?

    I am using WHM with CLOUDLINUX 7.2 x86_64 

    My IP address: 172.93.103.147 and 172.93.103.149

    I have checked all RBLs I could find and we're not listed. Hopefully you can help me find out the cause to see if we can make modifications, or if we should look elsewhere for a server. I would very much like to have help from your team or someone reading this.

    Thank you.

    Here's the detailed information I get:

     

     

    LOG: MAIN
      cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1aPFrl-002lkp-3S
    delivering 1aPFrl-002lkp-3S
    Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster8.eu.messagelabs.com [85.158.137.3] Connection timed out
    Connecting to cluster8.eu.messagelabs.com [85.158.139.35]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster8.eu.messagelabs.com [85.158.139.35] Connection timed out
    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.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 cluster8.eu.messagelabs.com [85.158.137.99]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster8.eu.messagelabs.com [85.158.137.99] 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.19]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster8.eu.messagelabs.com [85.158.139.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
    Connecting to cluster8a.eu.messagelabs.com [85.158.139.103]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster8a.eu.messagelabs.com [85.158.139.103] Connection timed out
    LOG: MAIN
      == olga.castro@adamselevator.com R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out
    LOG: MAIN
      cwd=/var/spool/exim 8 args: /usr/sbin/exim -v -t -oem -oi -f <> -E1aPFrl-002lkp-3S
    LOG: MAIN
      <= <> R=1aPFrl-002lkp-3S U=mailnull P=local S=2513 T="Warning: message 1aPFrl-002lkp-3S delayed 72 hours"
    LOG: MAIN
      cwd=/var/spool/exim 4 args: /usr/sbin/exim -v -Mc 1aQMd8-002ujN-R1
    delivering 1aQMd8-002ujN-R1
    LOG: MAIN
      => vp.purch <vp.purch@eevint.com> R=virtual_user T=virtual_userdelivery
    LOG: MAIN
      Completed

     



  • 2.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN
    Best Answer

    Broadcom Employee
    Posted Feb 02, 2016 05:08 PM

    Hello Josh, 

    With regards to this issue, both of your sending IPs were getting throttled due to high spam rate. We've seen spam traffic being sent from them as recent as Oct 29, 2015. I've just cleared them both, so you should no longer have problems connecting to our mail towers. 

    Regards, 

    Art



  • 3.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Feb 02, 2016 11:42 PM

    Thank you very much. I just bought this VDS server, I know many IPs are recycled, I try and do my best to run a tight ship with my users. Spam and mass mailings are a definite motive of cancellation. This server is being in use for the past 3-4 weeks, I hope we can relay messages correctly.

     

    Again, I appreciate very much your prompt response.



  • 4.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Mar 01, 2016 02:15 PM
      |   view attached

    Hello. I have reached this post becouse we have the same problem with our mail server. The ip addres is 52.32.113.158. We had problems with the mail server but now it is running again. Can you help us plaease.

    The log :

    Mar  1 13:09:05 ip-172-31-43-12 postfix/smtp[22949]: connect to cluster8.us.messagelabs.com[216.82.251.37]:25: Connection timed out

    Mar  1 13:09:05 ip-172-31-43-12 postfix/smtp[22950]: connect to cluster8.us.messagelabs.com[216.82.241.196]:25: Connection timed out

    Mar  1 13:10:05 ip-172-31-43-12 postfix/smtp[22950]: connect to cluster8.us.messagelabs.com[216.82.242.35]:25: Connection timed out

    Mar  1 13:10:05 ip-172-31-43-12 postfix/smtp[22949]: connect to cluster8.us.messagelabs.com[216.82.242.35]:25: Connection timed out



  • 5.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Broadcom Employee
    Posted Mar 01, 2016 03:10 PM

    Hello Carloshe, 

    I've adjusted reputation of your sending IP, so you should no longer be getting connection time out errors. This change will take effect in the next 30 minutes. 

     

     



  • 6.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Mar 19, 2016 02:17 AM

    Hello, I am the OP, the server has been moved to another IP address and we started getting a permanent error message:

    This message was created automatically by mail delivery software.

    The header: 

    Reporting-MTA: dns; mail.hostingbaja.com

    Action: failed
    Final-Recipient: rfc822;salomon.valdez@sensata.com
    Status: 5.0.0
    Remote-MTA: dns; cluster1.us.messagelabs.com
    Diagnostic-Code: smtp; 501 Connection rejected by policy [7.7] 5311, please visit www.messagelabs.com/support for more details about this error message.

    And the body text in the rejected message:

    A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

     

      salomon.valdez@sensata.com

        host cluster1.us.messagelabs.com [216.82.249.211]

        SMTP error from remote mail server after initial connection:

        501 Connection rejected by policy [7.7] 5311, please visit www.messagelabs.com/support for more details about this error message.

    The affected domains are: janisource.com.mx and borderassembly.com.mx and my current IP is this:

    206.221.191.155 with the DNS name: ns1.hostingbaja.com

    I appreciate the help you can provide to enable delivery of our emails. The reason we made the IP change was because the MTA was affecting us with that IP, we have enabled monitoring services with three separate vendors to ensure spam, virus and smtp delivery, DKIM and SPF are enabled and working on all servers.

    Thank you for your support.



  • 7.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Broadcom Employee
    Posted Mar 21, 2016 01:03 PM

    Hello Josh, 


    I've submitted a request to have restrictions lifted from your new IP. This should be done in the next 24 hours. 



  • 8.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Mar 21, 2016 08:49 PM

    Thank you so much, you've been very helpful.

     

     



  • 9.  RE: Connecting to cluster8.eu.messagelabs.com [85.158.137.3]:25 ... failed: Connection timed out (timeout=5m) LOG: MAIN

    Posted Jul 14, 2016 10:07 PM

    Hello, im havinf the same issues with our IP 169.45.171.75

     

    the error is the following. thanks for your help

     

     

    LOG: MAIN
      cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1bNh3m-0001LM-Jl
    delivering 1bNh3m-0001LM-Jl
    Connecting to cluster1.us.messagelabs.com [216.82.241.243]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1.us.messagelabs.com [216.82.241.243] Connection timed out
    Connecting to cluster1.us.messagelabs.com [216.82.242.44]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1.us.messagelabs.com [216.82.242.44] Connection timed out
    Connecting to cluster1.us.messagelabs.com [216.82.251.43]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1.us.messagelabs.com [216.82.251.43] Connection timed out
    Connecting to cluster1.us.messagelabs.com [216.82.249.179]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1.us.messagelabs.com [216.82.249.179] Connection timed out
    Connecting to cluster1.us.messagelabs.com [216.82.241.131]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1.us.messagelabs.com [216.82.241.131] Connection timed out
    Connecting to cluster1a.us.messagelabs.com [85.158.139.103]:25 ... failed: Connection timed out (timeout=5m)
    LOG: MAIN
      H=cluster1a.us.messagelabs.com [85.158.139.103] Connection timed out
    LOG: MAIN
      == carlos.felguerez@linamar.com <Carlos.Felguerez@Linamar.com> R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out