Email Security.cloud

 View Only
  • 1.  Connect to cluster5.eu.messagelabs.com[195.245.230.51]:25: Connection timed out

    Posted Oct 09, 2017 12:41 PM

    Hello.

    Outgoing emails from our server are blocked in messagelabs.com filters and therefore cannot send email to our business partners! We keep getting the following error connect to cluster5.eu.messagelabs.com[195.245.230.51]:25: Connection timed out.

    I have checked the symantec blacklist and it says that we do not have a negative reputation and therefore cannot be submitted for investigation. Could I please ask for unblocked our server's IP address?

    Our mail servers ip address is 139.162.131.12 and domain is mail.produkt-guiden.dk

    Thank You in advance.

    Best Regards 
    Toms Bugna



  • 2.  RE: Connect to cluster5.eu.messagelabs.com[195.245.230.51]:25: Connection timed out

    Broadcom Employee
    Posted Oct 10, 2017 05:15 AM

    If your IP address was blocked you would get an immediate "connection failed" rather than "connection timed out".  So this sounds like some kind of connectivity issue. Can you try doing a traceroute to that IP?

    Also, that host name has multiple IP addresses; is that the only one you can't connect to, or do you get the same result with all of them?

    cluster5.eu.messagelabs.com. 900 IN    A    193.109.255.99
    cluster5.eu.messagelabs.com. 900 IN    A    85.158.138.179
    cluster5.eu.messagelabs.com. 900 IN    A    193.109.254.3
    cluster5.eu.messagelabs.com. 900 IN    A    85.158.136.83
    cluster5.eu.messagelabs.com. 900 IN    A    85.158.139.163
    cluster5.eu.messagelabs.com. 900 IN    A    195.245.230.51

     



  • 3.  RE: Connect to cluster5.eu.messagelabs.com[195.245.230.51]:25: Connection timed out

    Posted Oct 10, 2017 06:40 AM

    Here are two traceroutes I made:

    First -

    traceroute to cluster5.eu.messagelabs.com (85.158.138.179), 30 hops max, 60 byte packets
     1  139.162.128.3 (139.162.128.3)  0.653 ms  0.667 ms  0.812 ms
     2  139.162.129.3 (139.162.129.3)  1.082 ms 139.162.129.7 (139.162.129.7)  0.895 ms  1.006 ms
     3  xe-2-2-0.er1.Frankfurt-FF1.symsaas.net (80.81.194.61)  0.827 ms  0.822 ms symantec.fra.ecix.net (62.69.146.92)  0.686 ms
     4  unknown-46-226-55.bb.symantec.net (46.226.55.13)  0.785 ms unknown-46-226-55.bb.symantec.net (46.226.55.15)  0.779 ms  0.771 ms
     5  unknown-46-226-55.bb.symantec.net (46.226.55.181)  8.297 ms unknown-46-226-55.bb.symantec.net (46.226.55.183)  8.247 ms unknown-46-226-55.bb.symantec.net (46.226.55.185)  1.393 ms
     6  mail169.messagelabs.com (85.158.138.179)  0.715 ms  0.761 ms  0.637 ms

     

    Second -

    traceroute to 195.245.230.51 (195.245.230.51), 30 hops max, 60 byte packets
     1  139.162.128.3 (139.162.128.3)  0.984 ms  0.920 ms  1.062 ms
     2  139.162.129.14 (139.162.129.14)  0.866 ms 139.162.129.16 (139.162.129.16)  0.845 ms 139.162.129.14 (139.162.129.14)  0.860 ms
     3  xe-2-2-0.er1.Frankfurt-FF1.symsaas.net (80.81.194.61)  0.825 ms symantec.fra.ecix.net (62.69.146.92)  0.785 ms xe-2-2-0.er1.Frankfurt-FF1.symsaas.net (80.81.194.61)  0.805 ms
     4  unknown-46-226-55.bb.symantec.net (46.226.55.15)  0.809 ms unknown-46-226-55.bb.symantec.net (46.226.55.13)  0.769 ms unknown-46-226-55.bb.symantec.net (46.226.55.15)  0.792 ms
     5  unknown-46-226-55.bb.symantec.net (46.226.55.185)  0.824 ms unknown-46-226-55.bb.symantec.net (46.226.55.181)  0.767 ms unknown-46-226-55.bb.symantec.net (46.226.55.187)  0.918 ms
     6  mail33.messagelabs.com (195.245.230.51)  0.715 ms  0.664 ms  0.549 ms

     



  • 4.  RE: Connect to cluster5.eu.messagelabs.com[195.245.230.51]:25: Connection timed out
    Best Answer

    Broadcom Employee
    Posted Oct 10, 2017 09:07 AM

    Hello Toms, 

     

    I've adjusted reputation on your sending IP. You should no longer be seeing connectivity issues when sending to MessageLabs clusters. 

     

    Regards, 

    SymArt