cluster5.eu.messagelabs.com Connection timed out

July 13, 2016, 12:16 am

≫ Next: connect to cluster8.us.messagelabs.com:25: Connection timed out

≪ Previous: Data Protection> Action > Route To

I need a solution

Hi,

We have a problem delivering mail to Messagelabs.

Our sending mail server is clean and not delivering spam, cross checked twice.

We already checked also your reputation service at the following addresss and reported that our IP is clean:

http://ipremoval.sms.symantec.com/lookup/

Can you please remove any block from this IP?

Server IP: 185.43.209.215

Still we are experiencing the following errors:

"action=delayed reason=connect to cluster5.eu.messagelabs.com[85.158.138.179]:25: Connection timed out"

"action=delayed reason=connect to cluster3.eu.messagelabs.com[85.158.139.3]:25: Connection timed out"

Thanks in advance for your collaboration.

paolo

↧

connect to cluster8.us.messagelabs.com:25: Connection timed out

July 13, 2016, 1:46 am

≫ Next: "#5.0.0 smtp; 553-you are trying to use me..." error with incoming emails from a MessageLabs customer

≪ Previous: cluster5.eu.messagelabs.com Connection timed out

I need a solution

Hi,

I have experienced the connection timed out problem when I send the following emails via the mail server 125.215.207.36. Please help me to check and fix it. Thanks.

Jul 12 11:05:32 mail postfix/smtp[25854]: connect to cluster8.us.messagelabs.com[216.82.251.44]:25: Connection timed out

Jul 12 11:06:03 mail postfix/smtp[25854]: connect to cluster8.us.messagelabs.com[216.82.242.45]:25: Connection timed out

Jul 12 11:06:33 mail postfix/smtp[25854]: connect to cluster8.us.messagelabs.com[216.82.251.37]:25: Connection timed out

Jul 12 11:07:03 mail postfix/smtp[25854]: connect to cluster8.us.messagelabs.com[216.82.242.35]:25: Connection timed out

Jul 12 11:07:33 mail postfix/smtp[25854]: connect to cluster8.us.messagelabs.com[216.82.241.132]:25: Connection timed out

Jul 12 11:07:33 mail postfix/smtp[25854]: DF60024A21: to=<hubertho@hfghk.com>, relay=none, delay=1570, delays=1418/1.2/151/0, dsn=4.4.1, status=deferred (connect to cluster8.us.messagelabs.com[216.82.241.132]:25: Connection timed out)

Jul 12 11:15:31 mail postfix/smtp[26261]: connect to cluster6.us.messagelabs.com[216.82.249.212]:25: Connection timed out

Jul 12 11:16:01 mail postfix/smtp[26261]: connect to cluster6.us.messagelabs.com[216.82.242.36]:25: Connection timed out

Jul 12 11:16:31 mail postfix/smtp[26261]: connect to cluster6.us.messagelabs.com[216.82.251.38]:25: Connection timed out

Jul 12 11:17:01 mail postfix/smtp[26261]: connect to cluster6.us.messagelabs.com[216.82.242.46]:25: Connection timed out

Jul 12 11:17:31 mail postfix/smtp[26261]: connect to cluster6.us.messagelabs.com[216.82.241.100]:25: Connection timed out

Jul 12 11:17:31 mail postfix/smtp[26261]: B28EE269E7: to=<philipchen@hanglung.com>, relay=none, delay=1611, delays=1461/0.04/150/0, dsn=4.4.1, status=deferred (connect to cluster6.us.messagelabs.com[216.82.241.100]:25: Connection timed out)

Jul 12 11:35:23 mail postfix/smtp[1765]: connect to cluster8.us.messagelabs.com[216.82.251.39]:25: Connection timed out

Jul 12 11:35:54 mail postfix/smtp[1765]: connect to cluster8.us.messagelabs.com[216.82.242.45]:25: Connection timed out

Jul 12 11:36:24 mail postfix/smtp[1765]: connect to cluster8.us.messagelabs.com[216.82.241.196]:25: Connection timed out

Jul 12 11:36:54 mail postfix/smtp[1765]: connect to cluster8.us.messagelabs.com[216.82.242.35]:25: Connection timed out

Jul 12 11:37:24 mail postfix/smtp[1765]: connect to cluster8.us.messagelabs.com[216.82.251.44]:25: Connection timed out

Jul 12 11:37:24 mail postfix/smtp[1765]: DF60024A21: to=<hubertho@hfghk.com>, relay=none, delay=3361, delays=3211/0.03/151/0, dsn=4.4.1, status=deferred (connect to cluster8.us.messagelabs.com[216.82.251.44]:25: Connection timed out)

Jul 12 11:45:23 mail postfix/smtp[2379]: connect to cluster6.us.messagelabs.com[216.82.241.100]:25: Connection timed out

Jul 12 11:45:53 mail postfix/smtp[2379]: connect to cluster6.us.messagelabs.com[216.82.249.212]:25: Connection timed out

Jul 12 11:46:23 mail postfix/smtp[2379]: connect to cluster6.us.messagelabs.com[216.82.251.38]:25: Connection timed out

Jul 12 11:46:53 mail postfix/smtp[2379]: connect to cluster6.us.messagelabs.com[216.82.242.36]:25: Connection timed out

Jul 12 11:47:23 mail postfix/smtp[2379]: connect to cluster6.us.messagelabs.com[216.82.242.46]:25: Connection timed out

Jul 12 11:47:23 mail postfix/smtp[2379]: B28EE269E7: to=<philipchen@hanglung.com>, relay=none, delay=3403, delays=3252/0.04/150/0, dsn=4.4.1, status=deferred (connect to cluster6.us.messagelabs.com[216.82.242.46]:25: Connection timed out)

Thomas

↧

"#5.0.0 smtp; 553-you are trying to use me..." error with incoming emails from a MessageLabs customer

July 14, 2016, 9:10 am

≫ Next: 501 Connection rejected by policy

≪ Previous: connect to cluster8.us.messagelabs.com:25: Connection timed out

I need a solution

Our client (AAA.com) doesn't use message labs at all. They deal via email with another company (BBB.com) that does. When John@BBB.com sends an email to Sarah@BBB.com, John@BBB.com will recieve an email bounce back with this error:

Diagnostic information for administrators:
Generating server: server.rbguiweg.com
sarah@aaa.com
cluster4.eu.messagelabs.com #<cluster4.eu.messagelabs.com #5.0.0 smtp; 553-you are trying to use me [server-11.tower-21.messagelabs 553-.com] as a relay, but I have not been configured to let 553-you [1.1.1.1, server.bbb.com] do this. 553-Please visit http://www.symanteccloud.com/troubleshooting for 553-more details about this error message and instructions 553 to resolve this issue. (#5.7.1)> #SMTP

Now this only happens when anyone at BBB.com sends AAA.com an email. BBB.com doesn't have this issue with any other of their clients, and AAA.com don't have any problems recieving emails from any of their other clients. Our client (AAA.com) doens't have any problems sending BBB.com an email.

Now, AAA.com PREVIOUSLY used MessageLabs, so we came to the conclusion that MessageLabs still thinks AAA.com is registered with them, and is trying to route the email to an old server, but we called MessageLabs, who confirmed this sometimes happens, but said the domain is not provisioned with them at all.

The technical people at BBB.com seem to think the problem is on our side, and we think the problem is on BBB.com's side.

Can anyone shed some light into what this error actually means, and what could be causing this to happen?

↧

501 Connection rejected by policy

July 14, 2016, 1:27 pm

≫ Next: messagelabs.com [216.82.249.51] Connection timed out

≪ Previous: "#5.0.0 smtp; 553-you are trying to use me..." error with incoming emails from a MessageLabs customer

I need a solution

Boa tarde,

Mudamos o servidor do e-mail e estou tentando enviar um e-mail para um cliente e retorna com a seguinte mensagem:

This message was created automatically by mail delivery software.

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:

host cluster4.us.messagelabs.com [216.82.242.179]

SMTP error from remote mail server after initial connection:

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

Como faço para conseguir enviar o e-mail?

Segue nosso IP: 198.136.59.226

Obrigada,

Att,

↧

messagelabs.com [216.82.249.51] Connection timed out

July 14, 2016, 5:19 pm

≫ Next: 501 Connection Rejected by Policy [7.7]

≪ Previous: 501 Connection rejected by policy

I need a solution

Hello we are sending emails to a customer but the emails stay in the mail qeue with this processing message

H=cluster9.us.messagelabs.com [216.82.249.51] Connection timed out
Connecting to cluster9.us.messagelabs.com [216.82.251.41]:25 ... failed: Connection timed out (timeout=5m)

Our IP is 169.45.171.75

can you please help?

thank you

JEGF

↧

501 Connection Rejected by Policy [7.7]

July 18, 2016, 10:19 am

≫ Next: messagelabs.com Connection timed out

≪ Previous: messagelabs.com [216.82.249.51] Connection timed out

I need a solution

Hello.

We had an email server moved over the weekend to a new setup and some email are being rejected with the "501 Connection Rejected" error.

IP: 198.136.59.226

Thank you.

↧

messagelabs.com Connection timed out

July 23, 2016, 9:29 am

≫ Next: 501 Connection rejected by policy [7.7]

≪ Previous: 501 Connection Rejected by Policy [7.7]

I need a solution

Hello

We're experiencing problems when sending to email addresses that use messagelabs.com MX. See below;

Previous Message: 1bQsBx-0005UT-RH: H=cluster3.eu.messagelabs.com [85.158.139.3] Connection timed out

This is happening for various accounts on our server which is sending from IP Address 88.202.228.72

I have used this;

http://ipremoval.sms.symantec.com/lookup/

to check on our IP and it tells there is no problem with the IP Address.

Can you please help us resolve this issue as it's causing me headaches!

Thanks

↧

501 Connection rejected by policy [7.7]

July 24, 2016, 11:11 pm

≫ Next: Attempting SMTP connection to [cluster9a.us.messagelabs.com : 25]... The connection timed out.

≪ Previous: messagelabs.com Connection timed out

I need a solution

Hi,

We provide web/email hosting for a client who is trying to email a certain address, but is getting rejected. Error code is:

Action: failed

Final-Recipient: rfc822;[xxxx]

Status: 5.0.0

Remote-MTA: dns; cluster9.us.messagelabs.com

Diagnostic-Code: smtp; 501 Connection rejected by policy [7.7] 4716, please visit www.messagelabs.com/support for more details about this error message.

The server IP address is 198.49.69.162. I have checked this against your IP removal tool (http://ipremoval.sms.symantec.com/lookup/) and it's not listed - says this IP does not have a bad reputation.

Can you tell me why our emails are bouncing?

↧

Attempting SMTP connection to [cluster9a.us.messagelabs.com : 25]... The connection timed out.

July 25, 2016, 7:22 am

≫ Next: Connect to cluster3.eu.messagelabs.com[194.106.220.35]:25: Connection timed out

≪ Previous: 501 Connection rejected by policy [7.7]

I need a solution

hello.

2 week ago our mail server was bruteforced and server IP got in the blacklist at bl.spamcop.net.

Trouble fixed now, IP delisted from BL.

Here http://ipremoval.sms.symantec.com/lookup/ and here

http://www.senderbase.org/lookup/ we have Email Reputation: Neutral.

But all of "cluster*.*.messagelabs.com" are ignoring our server IP.

Mon 2016-07-25 00:40:01: MX-record resolution of [lenovo.com] in progress (DNS Server: 127.0.0.1)...

Mon 2016-07-25 00:40:01: * P=010 S=001 D=lenovo.com TTL=(4) MX=[cluster9.us.messagelabs.com]

Mon 2016-07-25 00:40:01: * P=020 S=000 D=lenovo.com TTL=(4) MX=[cluster9a.us.messagelabs.com]

Mon 2016-07-25 00:40:01: Attempting MX: P=010 S=001 D=lenovo.com TTL=(4) MX=[cluster9.us.messagelabs.com]

Mon 2016-07-25 00:40:01: Attempting SMTP connection to [cluster9.us.messagelabs.com : 25]

Mon 2016-07-25 00:40:01: A-record resolution of [cluster9.us.messagelabs.com] in progress (DNS Server: 127.0.0.1)...

Mon 2016-07-25 00:40:01: D=cluster9.us.messagelabs.com TTL=(6) A=[216.82.249.35]

Mon 2016-07-25 00:40:01: Attempting SMTP connection to [216.82.249.35 : 25]

Mon 2016-07-25 00:40:01: Waiting for connection...

Mon 2016-07-25 00:40:22: Winsock Error 10060 The connection timed out.

Our IP is 62.152.69.157. Can you check it, plz.

Thank you.

↧

Connect to cluster3.eu.messagelabs.com[194.106.220.35]:25: Connection timed out

July 27, 2016, 3:52 am

≫ Next: Mail delivery failed: returning message to sender

≪ Previous: Attempting SMTP connection to [cluster9a.us.messagelabs.com : 25]... The connection timed out.

I need a solution

Hi,

Our mail server had a small spam issue and is now unable to send to your servers, could you review the below IP's for us they are no longer listed on any BL's

status=deferred (connect to cluster3.eu.messagelabs.com[194.106.220.35]:25: Connection timed out)

Server IP's :

88.208.220.177
88.208.221.126
88.208.220.102
88.208.221.216
88.208.222.165
88.208.222.192

Thanks

↧

Mail delivery failed: returning message to sender

August 2, 2016, 5:05 am

≫ Next: Firewall timeout when trying to send email

≪ Previous: Connect to cluster3.eu.messagelabs.com[194.106.220.35]:25: Connection timed out

I need a solution

This message was created automatically by mail delivery software.

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:

  user@domain.com
    host cluster5.us.messagelabs.com [216.82.250.51]
    SMTP error from remote mail server after initial connection:
    501 Connection rejected by policy [7.7] 10804, please visit www.messagelabs.com/support for more details about this error message.
  user@domain.com
    host cluster5.us.messagelabs.com [216.82.250.51]
    SMTP error from remote mail server after initial connection:
    501 Connection rejected by policy [7.7] 10804, please visit www.messagelabs.com/support for more details about this error message.

Reporting-MTA: dns; altar30.supremepanel30.com

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

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

Our Server IPs are:

198.23.60.180

198.23.61.195

Thank you

Rahmat Shah Masror

↧

Firewall timeout when trying to send email

August 2, 2016, 12:00 pm

≫ Next: Symantec.Cloud - Question About Notifications

≪ Previous: Mail delivery failed: returning message to sender

I need a solution

Hi,

We recently moved to a new Dedicated Server and we are having issues delivering mail to your messagelabs.com servers.

Our IP is 72.9.154.92 and we have only been using it for the last month.

LOG: MAIN
H=cluster4.us.messagelabs.com [216.82.242.33] Connection timed out
Connecting to cluster4.us.messagelabs.com [216.82.251.33]:25 ... failed: Connection timed out (timeout=5m)

Thanks

↧

Symantec.Cloud - Question About Notifications

August 3, 2016, 6:44 pm

≫ Next: EU and US Messagelabs.com Connection Issue

≪ Previous: Firewall timeout when trying to send email

I need a solution

With Symantec.Cloud (messagelabs), is it possible to have one email notification for each user as opposed to one notification for every user's alias. For example, right now the user a user has two alias (jdoe@xyz.com and joedoe@xyz.com) and he receives a daily notification email for each. Is it possible to consolidate them?

Thanks!!

↧

EU and US Messagelabs.com Connection Issue

August 4, 2016, 2:12 am

≫ Next: forwarding not working anymore

≪ Previous: Symantec.Cloud - Question About Notifications

I need a solution

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 ~]#

↧

forwarding not working anymore

August 11, 2016, 2:29 am

≫ Next: 501 Connection Rejected by Policy [7.7]

≪ Previous: EU and US Messagelabs.com Connection Issue

I need a solution

Dear all, 　

were using symantec.cloud for our example.de domain. 　

since a long time were succeffully forawarding emails from our example.fr domain to example.de domain.　

before 2 weeks the ip of the .fr was listed in pbl - after the removal everything worked properly again. close after the removal were receiving nothing anymore... even no mailer deamon trying to send a mail @ example.fr...　

i'm really lost at the moment - nothing makes sense...　

forwarding example.fr to example.de is not working　

forwarding example.fr to gmail.com - is WORKING　

forwading gmail.com to example.de - is WORKING　

sending direct mail from example.fr to example.de - is WORKING　

using an autoresponder on example.fr - receiving that on example.de - is WORKING　

checking symantec - nothing new / no changes....　

the forwarding of the example.fr is not working... the email just gets lost....???!!!　

can anybody help?　

THANKS!　

↧

501 Connection Rejected by Policy [7.7]

August 22, 2016, 12:10 am

≫ Next: Settings in Security.cloud to accept mails from Network Prevent for Email

≪ Previous: forwarding not working anymore

I need a solution

Dear Symantec-Team,

We had an email server going live last week and some email are being rejected with the "501 Connection Rejected" error.

IP:

178.16.56.48

178.16.56.49

188.94.249.252

Could you please delist them, were not on any RBL

Thank you.

↧

Settings in Security.cloud to accept mails from Network Prevent for Email

August 28, 2016, 7:29 am

≫ Next: cluster5.eu.messagelabs.com operation time out

≪ Previous: 501 Connection Rejected by Policy [7.7]

I need a solution

Hello all,

Trying to setup below mail flow and integrate On premise DLP server with to monitor outbound email traffic from office 365 to symantec security.cloud.

Below is the flow.

Outbound mails from my org -> Office 365 -> Network Prevent for Email (my org's DMZ) -> Office 365 -> Symantec Email Security.cloud -> Internet

What are the IP addresses that I have to provide in Network Prevent for Email Server to foward the mails to Symantec Security.cloud?

What are the settings I need to do to accept emails from On-Premise Network Prevent for Email server (this server will be on-prem DMZ with a public IP)

↧

cluster5.eu.messagelabs.com operation time out

August 30, 2016, 3:42 am

≫ Next: Can not reach Support Team

≪ Previous: Settings in Security.cloud to accept mails from Network Prevent for Email

I need a solution

I'm having a Mail Server with ospedale.perugia.it domains on it and sending Mail's to different reciepients are getting this error message:

(connect to cluster5.eu.messagelabs.com[85.158.136.83]:25: Operation timed out)

Can you help me

My IP is 88.56.33.39

Kind regards

Walter Picchio

↧

Can not reach Support Team

September 4, 2016, 9:50 am

≫ Next: Cant open ticket or chat

≪ Previous: cluster5.eu.messagelabs.com operation time out

I need a solution

Hi All,

Please advise me how to reach support.

Sending email on support.cloud@ says that "support will no longer respond to emails"

When I try to click on Link https://clients.messagelabs.com/Support/Ticketing/... after logging in to my management console I get below error, same goes for chat link. It is impossible to reach support.

↧