Help connect to clusterX.us.messagelabs.com Connection timed out

June 30, 2017, 9:39 am

≫ Next: blacklist

≪ Previous: 501 Connection rejected by policy [7.7] (IP Blacklist Removal)

$

0

0

I need a solution

hi  messagelabs

Our mail server mail.ruihesoft.com 112.65.245.173 can not send email to our customers and suppliers who use messagelabs.com this month
It maybe block by messagelabs.com 
Please help

postfix log 

 postfix/smtp[31764]: connect to cluster6.us.messagelabs.com[216.82.251.38]:25: Connection timed out

 postfix/smtp[31764]: connect to cluster6.us.messagelabs.com[216.82.249.212]:25: Connection timed out

 postfix/smtp[31764]: connect to cluster6.us.messagelabs.com[216.82.242.46]:25: Connection timed out

postfix/smtp[31764]: AB0F12026C: to=<cherry.lu@autodesk.com>, relay=none, delay=105, delays=0.07/0/105/0, dsn=4.4.1, status=deferred (connect to cluster6.us.messagelabs.com[216.82.242.36]:25: Connection timed out)

 postfix/smtp[32549]: connect to cluster6.us.messagelabs.com[216.82.242.36]:25: Connection timed out

postfix/smtp[639]: connect to cluster6.us.messagelabs.com[216.82.241.100]:25: Connection timed out

0

---

blacklist

July 3, 2017, 1:59 am

≫ Next: IP relisted & cant de-list

≪ Previous: Help connect to clusterX.us.messagelabs.com Connection timed out

$

0

0

I need a solution

Hi, this ip are in your BL but not sending spam, please delist

51.255.23.164

51.255.23.165

37.59.129.124

37.59.129.125

37.59.129.126

37.59.129.127

193.70.58.176

193.70.58.177

193.70.58.178

193.70.58.179

i use your tools but after two days they are re-entered in the black list despite being machines...

thanks

Giorgio

0

IP relisted & cant de-list

July 2, 2017, 1:59 pm

≫ Next: Fake Blacklist

≪ Previous: blacklist

$

0

0

I need a solution

Hi

My IP "162.214.16.233" keeps getting blacklisted daily & now I can't de-list it. Its currently not on any other blacklist apart from symantec. This is the bounce back email:

This is the mail delivery agent at Symantec Email Security.cloud.

I was unable to deliver your message to the following addresses:

arti.asharma@vodafone.com.fj

Reason: 550 Message refused by Trustwave SEG SpamProfiler

The message subject was: [Suspected Spam]: VODAFONE FIJI LTD The message date was: Thu, 15 Jun 2017 12:31:47 +1200 The message identifier was: 8C/03-01999-9F3D1495 The message reference was: server-12.tower-188.messagelabs.com!1497486323!113655423!9

Please do not reply to this email as it is sent from an unattended mailbox.

Contact your email administrator if you need more information, or instructions for resolving this issue.

Please help resolve this

0

Fake Blacklist

July 3, 2017, 1:10 am

≫ Next: messagelabs.com Connection timed out

≪ Previous: IP relisted & cant de-list

$

0

0

I need a solution

Good morning,

After months of research I came to this thread since writing does not answer anyone.

As I have been saying for months we are penalized on many VIRUS FREE, NO OPEN RELAY servers that comply with all the security rules without sending spam as your filter as it can be seen from all users who write DO NOT WORK.

Now if something does not work, the simplest thing to do is turn it off and turn it back on once.

I will send you all our IPs for which you only consider to be malicious and for which I am looking forward to being removed from the black list:

51.255.23.164

51.255.23.165

37.59.129.124

37.59.129.125

37.59.129.126

37.59.129.127

193.70.58.176

193.70.58.177

193.70.58.178

193.70.58.179

0

messagelabs.com Connection timed out

July 3, 2017, 5:18 pm

≫ Next: Have you had your email stopped as spam and you believe this is incorrect?

≪ Previous: Fake Blacklist

$

0

0

I need a solution

Hello

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

cluster4a.us.messagelabs.com[216.82.251.230]:25: Connection timed out

I tried to connect by telnet...

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

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.

The IP address you submitted, 52.187.61.132, does not have a negative reputation and therefore cannot be submitted for investigation.

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

Thanks

0

Have you had your email stopped as spam and you believe this is incorrect?

July 4, 2017, 1:21 am

≫ Next: MessageLabs

≪ Previous: messagelabs.com Connection timed out

$

0

0

I do not need a solution (just sharing information)

If you have seen your mail stopped with a 553 message filtered error this means we have deemed that mail to potentially be spam and have stopped it as such.

 

If you believe we have stopped this incorrectly and you are a Symantec Email Security.Cloud client please follow this process in order to address this issue.

https://support.symantec.com/en_US/article.TECH233678.html

 

If you believe we have stopped this incorrectly but you are not a Symantec client we can still assist you. Please follow the process in this link

https://support.symantec.com/en_US/article.TECH82881.html

Thank you

0

MessageLabs

July 4, 2017, 6:39 am

≫ Next: 553 MESSAGE FILTERED 5.7.1

≪ Previous: Have you had your email stopped as spam and you believe this is incorrect?

$

0

0

I need a solution

Dears,

I support a web application tool for company clients where it's required to confirm their information on registration proccess by replying to confirmation email . 

IP: 194.58.96.144

DNS: sales-puratos.ru

The web tool able to send mails to any public email services besides corporate domain *@puratos.com which is behind MessageLabs infrastructure. 

Main reason always remains the same:

501 Connection rejected by policy [7.7] XXXXX, please visit www.messagelabs.com/support...

I've double checked follow:

• IP is not black listed on any SBL's and DNS as well.
• Symantec IP investigation tool shows NO negative reputation of mentioned IP
• I've also sent email with de list request to: investigation@review.symantec.com with reply:
• "....We will investigate and if necessary setup counter measures to make sure that it is not blocked again in the future. The reason for your IP being identified as a zombie is that Symantec received what appears to be spam email traffic from your IP into its Probe Network and performed a series of tests to determine if your IP address was a mail server. Upon failing this initial test, we performed additional analysis of the email traffic prior to listing the IP."
• Web app. don't act as open relay

Email still don't reach any recepient within @puratos.com domain

I'll be apreciate You to investigate my case and release domain\IP form black lists.

Regards, 

0

553 MESSAGE FILTERED 5.7.1

July 4, 2017, 8:19 am

≫ Next: 501 Connection rejected by policy [7.7] 16316

≪ Previous: MessageLabs

$

0

0

I need a solution

Hi,

I'm hoping someone in Tier 2 can help us. We are getting blocked when sending to ANY customer that uses Symantec.Cloud. The error is 

#553-Message filtered. 

I've attached a screenshot and have talked to Kevin about this.

Thanks!

Eric

0

• Email_Block.jpg

---

501 Connection rejected by policy [7.7] 16316

July 5, 2017, 10:27 pm

≫ Next: MessageLabs Email IP Ranges

≪ Previous: 553 MESSAGE FILTERED 5.7.1

$

0

0

I need a solution

Hello,
 

I've problem sent email to some providers, it always said "SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 16316, please visit www.messagelabs.com/support"

I Already test the IP Lookup at http://ipremoval.sms.symantec.com/lookup/ and found my IP Address is not in list.

I hope you can help me to remove my IP Address 107.174.244.61 from your Blacklist.

Thank you for your attention.

Regrads,

Furqon . SY

0

MessageLabs Email IP Ranges

July 6, 2017, 10:18 am

≫ Next: IP Reputation

≪ Previous: 501 Connection rejected by policy [7.7] 16316

$

0

0

I need a solution

I need some help. We have a couple of clients who appear to be behind the messagelabs infrastructure which seems to be hosted in the UK and Germany. My network team basically blocks everything out of europe because we are a small US organization and they dont see why someone from europe would be emailing them (dont get me started!).

Anyway, I am 100% sure that emails coming to us from @erm.com and @soncellna.com are being dropped by our firewall. So I need a list of IPs or IP ranges that email could be sending emails from messagelabs. That way i can get these ips or ranges to the firewall team and they can allow traffic from them. 

I only need Email ranges, or whatever would be sending out of the messagelabs infrastructure. 

Thanks for the help!

0

IP Reputation

July 10, 2017, 9:00 am

≫ Next: Bad reputation due to snow shoe spamming, but not compromised

≪ Previous: MessageLabs Email IP Ranges

$

0

0

I need a solution

Hello,

i am a devops/admin and one of my clients has the problem that the reputation of the server ip is again bad (snowshoe spam).

The server is monitored and not compromised.

Is there a chance that someone here can help?

I can provide the bounce mail information by private message.

Emails to Investigation@review.symantec.com are not replied by symantec, although i see they are delivered to symantec incoming mail servers correctly from my ip.

I can remove the ip but it -maybe- will happen again and again..

Thank you.

Thomas

0

Bad reputation due to snow shoe spamming, but not compromised

July 13, 2017, 12:44 am

≫ Next: Symmantec Cloud Blacklist Removal

≪ Previous: IP Reputation

$

0

0

I need a solution

I'm maintaining a personal (Zimbra based) mailserver that serves a couple of domains for me and some friends. The server is part of a VM infrastructure that has 4 ip addresses to share among some VM's. All of these IP's have been blacklisted by symantec because of suspected snow shoeing spam, while only 2 of these IP's send out mails (the other is a Sympa based mailinglist server, rarely used). I've looked at the mail logs of both servers and can't for the life of me find any abnormal mails? I've checked RBL listing on mxtoolbox and none of my IP's are listed on any RBL? SPF records are all correct for these servers.

I requested delisting once and was delisted (but only after having spent some time typing a personal message instead of just clicking the 2 checkboxes that I've done my homework). Now, I'm back on the list and me and my friends can't send mails to the mailservers of KPN (mailin.kpnmail.nl).

host mailin.kpnmail.nl[213.75.3.30] refused to talk to me: 421 5.5.0 Your IP has been blacklisted. Please contact abuse@kpn.com for more information.
 

Yesterday I started the delisting procedure again, but have yet to see the result. I'm completely at a loss what to do next? It's frustrating to maintain a simple (well maintained!) mailserver these days having to battle these false positives all the time.

Involved ip range: 94.103.150.236-239

0

Symmantec Cloud Blacklist Removal

July 13, 2017, 10:58 pm

≫ Next: server...messagelabs.com returned an error > 553 (emails rejected)

≪ Previous: Bad reputation due to snow shoe spamming, but not compromised

$

0

0

I need a solution

Hi There,

I am posting on behalf of our client with the domain name of coldxpress.com.au. as they are receiving bounceback messages from every single organisation that is currently using Symmantec cloud email filtering.

If needed I can provide bounceback messages and error logs.

The domain is currently running from office 365. We have checked everything on our domain as well as many public blacklists which are all normal.

If this domain could be taken off of the blacklist as soon as possible we would appreciate it as the staff cannot send email to many business which are running your system.

0

server...messagelabs.com returned an error > 553 (emails rejected)

July 13, 2017, 9:14 pm

≫ Next: Moved server to new IP; emails are now being marked as spam by Email Security .Cloud (formerly MessageLabs)

≪ Previous: Symmantec Cloud Blacklist Removal

$

0

0

I need a solution

I need help. I have a new laptop with new subscriptions to Office 365 and to Norton Internet Security.  And, now I have a new problem, but only when I send an email to one person's business email.

About half of my emails to him are rejected. Some have attachments, and some don't. I've never had this problem before, and neither has the email receipient. This is the message:

It says: "server-16.tower-131.messagelabs.com error-> 553 you are trying to use me as a relay, but I have not been configured to let you" [then there is a string of numbers followed by] "outbound.protection.outlook.com do this. Please visit www.symanteccloud.com/troubleshooting for more details about this error message and instructions to resolce this issue. (#5.7.1)" I have seen similar errors on the website, but not this exact problem. 

The recipient says the problem is on my end.  I don't know how to fix it. Can you help me?

0

Moved server to new IP; emails are now being marked as spam by Email Security .Cloud (formerly MessageLabs)

July 14, 2017, 9:30 am

≫ Next: Email being blocked - 553 Message filtered

≪ Previous: server...messagelabs.com returned an error > 553 (emails rejected)

$

0

0

I need a solution

We recently moved our mail server to a new IP (5.39.25.177) and it seems that email from our new IP to Email Security Cloud is now being marked as spam.

We've checked the IP with http://ipremoval.sms.symantec.com/lookup/ and was initially listed (not anymore), but mail seems to continue being marked as spam.

0

---

Email being blocked - 553 Message filtered

July 14, 2017, 2:09 pm

≫ Next: Messages marked as spam. Reason : tests=ipchecker

≪ Previous: Moved server to new IP; emails are now being marked as spam by Email Security .Cloud (formerly MessageLabs)

$

0

0

I need a solution

Email from our domain (knightstone.co.uk) sent via our Office365 email service to exchange online users who are unable to send out email.

Error Details

Reported error: 550 5.0.350 Remote server returned an error -> 553 you are trying to use me [server-15.tower-180.messagelab;s.com] as a relay, but I have not been configured to;let you [213.199.154.113, mail-am5eur03lp0113.outbound.p;rotection.outlook.com] do this. Please visit;www.symanteccloud.com/troubleshooting for more details;about this error message and instructions to resolve;this issue. (#5.7.1) DSN generated by: AM5PR0902MB2065.eurprd09.prod.outlook.com Remote server: server-15.tower-180.messagelabs.com

We have enabled Static route on MessageLabs with confirmation that test email worked.

Please can we get the block lifted??

Thanks!

0

Messages marked as spam. Reason : tests=ipchecker

July 16, 2017, 10:32 am

≫ Next: Connection rejected by policy [7.7] 14310

≪ Previous: Email being blocked - 553 Message filtered

$

0

0

I need a solution

Hello,

We have an uncompromised mailserver with four IPs:
- 212.129.48.30
- 212.129.48.31
- 212.129.48.32
- 212.129.48.33
Our IPs are not listed on any blacklists (very good reputation on SenderScore), and the server have been scanned thoroughly and is clean.

Our messages are marked as spam by Email Security.Cloud with the following reason : "X-SpamReason: Yes, hits=50.0 required=7.0 tests=ipchecker: aGl0YW5kcnVuX2JpdF92ZWN0b3I=".

Here is an example :

X-Msg-Ref	server-11.tower-179.messagelabs.com!1500221569!93926717!1
X-OriginalArrivalTime	16 Jul 2017 16:12:49.0209 (UTC) FILETIME=[5E6A3A90:01D2FE4E]
X-Originating-IP	[212.129.48.33]
X-Spam-Flag	YES
X-SpamInfo	spam detected heuristically
X-SpamReason	Yes, hits=50.0 required=7.0 tests=ipchecker: aGl0YW5kcnVuX2JpdF92ZWN0b3I=
X-StarScan-Received
X-StarScan-Version	9.4.25; banners=-,-,-

What can we do to resolve this issue ?

Regards,

0

Connection rejected by policy [7.7] 14310

July 16, 2017, 6:22 pm

≫ Next: Our whole subnet has a negative reputation due to snow shoe spamming techniques

≪ Previous: Messages marked as spam. Reason : tests=ipchecker

$

0

0

I need a solution

Hi 

Request for Delisting for our IP address - 192.99.173.244

BFFC79BA0294   450920 Thu Jul 13 14:08:23  
(host cluster9.us.messagelabs.com[216.82.251.41] refused to talk to me: 501 Connection rejected by policy [7.7] 14310, please visit www.messagelabs.com/support for more details about this error message.)
                                         cris_isirani@cathaypacific.com
                                         jojo_veneracion@cathaypacific.com

Regards

0

Our whole subnet has a negative reputation due to snow shoe spamming techniques

July 17, 2017, 9:56 am

≫ Next: Problems with Emails going through messagelab servers

≪ Previous: Connection rejected by policy [7.7] 14310

$

0

0

I need a solution

Hi,
a lot of customers are complaining that they can't sed email to specific domains.
These domains are using your appliance as anti-spam

My MX servers are perfectly clean on every RBL or health check (mxtoolbox and dnsstuff.com).

I made a lot of queries of our subnet and i found that all of my IP address have a negative reputation!

"The host has been observed sending spam in a format that is similar . to snow shoe spamming techniques."

How's that possible? 90% of them are not even in use.  The ip that we are talking is: 185.132.68.51.

I would like to resolve this problem ASAP because as a Service
Provider we are receiving a lots of complaints from multiple
customers.

0

Problems with Emails going through messagelab servers

July 17, 2017, 8:14 pm

≫ Next: Email being blocked wrongly - 501 Connection rejected by policy [7.7]

≪ Previous: Our whole subnet has a negative reputation due to snow shoe spamming techniques

$

0

0

I need a solution

Hi,

My customer's email server  (  119.73.162.37  )  when connect to  the messagelabs   servers will have the following  errors

Jul 18 10:54:17 XXXXX postfix/smtp[6955]: 4BA6E8000BC59: to=<XXX@jXXX.com>, relay=cluster1.us.messagelabs.com[216.82.249.179]:25, delay=912, delays=711/0/201/0, dsn=4.4.2, status=deferred (lost connection with cluster1.us.messagelabs.com[216.82.249.179] while receiving the initial server greeting)

This has been happening since  15 July 2017.   I  have checked that the email server   119.73.162.37 does not have any bad reputation on http://ipremoval.sms.symantec.com/lookup/

The IP address you submitted, 119.73.162.37, does not have a negative reputation and therefore cannot be submitted for investigation. 

Please help .

thks

Jimmy

0