501 Connection rejected by policy [7.7]

September 20, 2016, 2:13 am

≫ Next: 501 Connection rejected by policy [7.7]

≪ Previous: connect to cluster14.us.messagelabs.com[216.82.241.197]:25: Connection refused

I need a solution

Hello,

Our emails sent to one of our business partners are getting filtered with delivery error "501 Connection rejected by policy [7.7]".

Here is a quick log of example: "host cluster5.eu.messagelabs.com [193.109.255.99]
SMTP error from remote mail server after initial connection:
501 Connection rejected by policy [7.7] 4802, please visit <http://www.messagelabs.com/support> www.messagelabs.com/support for more details about this error message."
"

Our mail server is properly configured and not blacklisted in anyway (from what we know).
I have tried contact your support, but im unable to find any information about how do this. I even try contact by phone, but the operator doesn't even know what im talking (possible becouse was only to clients with active services).

I have tried use your "IP Investigation Request" system, but doesn't appears to work, as the IP gets listed again and with no new email sent.

Is possible check your system and authorize our IP address 176.31.217.177, or let us know what actually triggerred the block so we can take corrective action.

Thanks

↧

501 Connection rejected by policy [7.7]

September 22, 2016, 3:18 am

≫ Next: PBE (Policy Based Encryption) on Symantec.Cloud

≪ Previous: 501 Connection rejected by policy [7.7]

I need a solution

Our twoMailserverIPaddress(84.200.59.209and84.200.59.210)will be blockedfrom youwith the message:

Connectionrejectedbypolicy [7.7]

Why is that?Wearenot on anyknown to us Blacklists.Wecan not reachmany of our customers.

1474960905

↧

PBE (Policy Based Encryption) on Symantec.Cloud

September 23, 2016, 2:59 am

≫ Next: 501 Connection rejected by policy [7.7]

≪ Previous: 501 Connection rejected by policy [7.7]

I need a solution

Hello Folks,

Here is a small synopsis.

My client wants to have PBE for users sending email to external domains.

Currently using Symantec Message Labs (Symantec.Cloud) as a gateway for anit spam and anti malware.

Questions:

1. Do i need a third party SSL cert to enable or activate PBE on message labs (post i purchase the PBE solution)

2. What type of certificate is required if required.

Regards

Paul Sathya

↧

501 Connection rejected by policy [7.7]

September 27, 2016, 9:59 am

≫ Next: Emails are being blocked - 553 Message filtered

≪ Previous: PBE (Policy Based Encryption) on Symantec.Cloud

I need a solution

Hello,

A client that we host is currently experiencing issues with the IP address of their server being rejected when they attempt to send mail to their clients.

Information:

Server IP Address: 199.59.56.43

Here are the full mail headers for one of these rejections:

Return-path: <>

Envelope-to: lucy@drlucyford.com

Delivery-date: Tue, 27 Sep 2016 10:32:55 -0500

Received: from mailnull by shared7.hostwindsdns.com with local (Exim 4.87)

id 1bouNL-0002mn-OC

for lucy@drlucyford.com; Tue, 27 Sep 2016 10:32:55 -0500

X-Failed-Recipients: Sally.Solis-Cohen@biworldwide.com

Auto-Submitted: auto-replied

From: Mail Delivery System Mailer-Daemon@shared7.hostwindsdns.com

To: lucy@drlucyford.com

Content-Type: multipart/report; report-type=delivery-status; boundary=1474990375-eximdsn-1661565011

MIME-Version: 1.0

Subject: Mail delivery failed: returning message to sender

Message-Id: E1bouNL-0002mn-OC@shared7.hostwindsdns.com

Date: Tue, 27 Sep 2016 10:32:55 -0500
--1474990375-eximdsn-1661565011

Content-type: text/plain; charset=us-ascii
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:
Sally.Solis-Cohen@biworldwide.com

host cluster6.us.messagelabs.com [216.82.242.46]

SMTP error from remote mail server after initial connection:

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

Content-type: message/delivery-status
Reporting-MTA: dns; shared7.hostwindsdns.com
Action: failed

Final-Recipient: rfc822;Sally.Solis-Cohen@biworldwide.com

Status: 5.0.0

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

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

Content-type: message/rfc822
Return-path: lucy@drlucyford.com

Received: from [129.68.225.198] (port=55436 helo=LAPTOPQACCLO7O)

by shared7.hostwindsdns.com with esmtpsa (TLSv1:AES256-SHA:256)

(Exim 4.87)

(envelope-from lucy@drlucyford.com)

id 1bouNL-0002mf-Dv

for Sally.Solis-Cohen@biworldwide.com; Tue, 27 Sep 2016 10:32:55 -0500

From: "Lucy R. Ford" lucy@drlucyford.com

To: "'Solis-Cohen, Sally'" Sally.Solis-Cohen@biworldwide.com

References: D40FFE1B.20A9B%sally.solis-cohen@biworldwide.com

In-Reply-To:

Subject: FW: PSPS follow up

Date: Tue, 27 Sep 2016 11:32:56 -0400

Organization: LRFord Consulting LLC

Message-ID: 002c01d218d4$6c278b70$4476a250$@drlucyford.com

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----=_NextPart_000_002D_01D218B2.E51B42A0"

X-Mailer: Microsoft Outlook 16.0

Thread-Index: AQJQm7JcWEydm+GV/guevgWSjnQ9aAHyAvTrn4DhKgA=

Content-Language: en-us

↧

Emails are being blocked - 553 Message filtered

October 7, 2016, 11:21 am

≫ Next: Boxed.com emails being blocked

≪ Previous: 501 Connection rejected by policy [7.7]

I need a solution

Hello there. Emails from our domain have recently been being blocked by many of our clients. The domain is cmginc.com and filter/block message is below:

The error that the other server returned was:
553-Message filtered. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)

↧

Boxed.com emails being blocked

October 12, 2016, 8:20 am

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

≪ Previous: Emails are being blocked - 553 Message filtered

I need a solution

We're seeing blocked emails by our clients, both inbound and outbound. I've sent three examples to CLOUDfeedback@feedback-87.brightmail.com.

Just wanted to post in here to increase visibility on this issue.

Example 1:

From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
Date: Tue, Oct 11, 2016 at 10:13 AM
Subject: Delivery Status Notification (Failure)
To: XXXXXXXX@boxed.com

Delivery to the following recipient failed permanently:

XXXXXXXXXXXX@diageo.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain diageo.com by cluster3.eu.messagelabs.com. [85.158.136.3].

The error that the other server returned was:
553-Message filtered. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)

Example 2:

From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>

Date: Wed, Oct 12, 2016 at 10:08 AM

Subject: Delivery Status Notification (Failure)

To: XXXXXXX@boxed.com

Delivery to the following recipient failed permanently:

XXXXXXXXXX@jpmorgan.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain jpmorgan.com by cluster14.us.messagelabs.com.[216.82.248.67].

The error that the other server returned was:
553-Message filtered. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)

Example 3:

Not sure of time, but was sent Wednesday October 12.

rb.com -> boxed.com

The following organization rejected your message: server-12.tower-38.messagelabs.com.

↧

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

October 13, 2016, 5:47 pm

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

≪ Previous: Boxed.com emails being blocked

I need a solution

We're using Postfix on a Linux server to send emails via SMTP. Emails are relayed from our server via Office365. Most emails reach their destination fine, however certain addresses never receive our emails. When I check the mailq I see the following:

$ sudo mailq
[sudo] password for peter:
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
F41CB12A959     2271 Fri Oct 14 00:04:14  root@ourserver.com.au
(connect to cluster8.us.messagelabs.com[216.82.242.37]:25: Connection timed out)anyaddress@bp.com

B77A512A92C   546675 Wed Oct 12 00:10:06  support@ourserver.com.au
(connect to cluster8.us.messagelabs.com[216.82.249.147]:25: Connection timed out)anyaddress@sgfleet.com

-- 537 Kbytes in 2 Requests.

I'm not keen to post our IP address in a public forum like this, however the email Queue IDs there are correct if that helps to identify things at your end. I can give you our IP or hostname in a private message if you need it.

I have checked the blacklists on mxlookup.com and our domain has all green ticks (nobody is blacklisting us). Also I have checked our IP address here: http://ipremoval.sms.symantec.com/lookup/ and it says The IP address you submitted, xxx.xxx.xxx.xxx, does not have a negative reputation and therefore cannot be submitted for investigation.

Please help.

↧

501 Connection rejected by policy [7.7] 5516

October 16, 2016, 8:08 am

≫ Next: Mail server filtered 501 Connection rejected by policy [7.7] 20115

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

I need a solution

Can we please get this investigated.

We control this server and it is hosting 1 single domain for a canadian magazine. It is causing a lot of issues as we cannot seem to send invoices and contact some of our clients. We barely send emails.

IP is not balcklisted, it's reputation seems to ge good and we controlled it for the past 12 months so we do not understand this tag.

Server IP: 5.135.3.164

Reporting-MTA: dns; server.revistamar.com

Action: failed
Final-Recipient: rfc822;cmonteiro@bothwell-accurate.com
Status: 5.0.0
Remote-MTA: dns; cluster4.us.messagelabs.com
Diagnostic-Code: smtp; 501 Connection rejected by policy [7.7] 5516

Greatly appreciated.

↧

Mail server filtered 501 Connection rejected by policy [7.7] 20115

October 16, 2016, 1:05 pm

≫ Next: Emails rejected : 553-Message filtered

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

I need a solution

Hello,

We've been facing issues when our company try to deliver mail to symantec-protected mail servers.

We are not listed on any blacklist and we are using SPF and DKIM (our mail is properly deliver to all other plateforms except symantec).

Please can you remove our mail server 212.83.167.241 from your blacklist as it is really a problem for us when we try to send legitimate mail to our clients from our corporate server.

Thanks in advance

Bruno

↧

Emails rejected : 553-Message filtered

October 18, 2016, 8:59 am

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

≪ Previous: Mail server filtered 501 Connection rejected by policy [7.7] 20115

I need a solution

Hello,

One of our client cannot send message to emails addresses with MX *.messagelabs.com.

His domain is : ix-orp.net

Bounce message :

553-Message filtered. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)

I already forward message to cloudfeedback@feedback-87.brightmail.com.

Thank you

↧

501 Connection rejected by policy [7.7] 9207

October 21, 2016, 2:57 pm

≫ Next: 5.1.0 - Unknown address error 553-'SPF

≪ Previous: Emails rejected : 553-Message filtered

I need a solution

Hello,

Our emails sent to our clients are getting filtered with delivery error "501 Connection rejected by policy [7.7]".

We don't have bad reputation :

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

Could you help me to check problem why our emails are blocked ?

WIth Best Regard

Michał Wojciechowski

↧

5.1.0 - Unknown address error 553-'SPF

October 24, 2016, 10:14 am

≫ Next: blocked IP - 501 Connection rejected by policy [7.7] 17903

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

I need a solution

Hi,

Problem sending emails to one of our client since Thursday. Got the bounced back message:

5.1.0 - Unknown address error 553-'SPF (Sender Policy Framework) domain authentication\nfail. Refer to the Troubleshooting page at\nhttp://www.symanteccloud.com/troubleshooting for more\ninformation. (#5.7.1)'

We were trying to send over 100 messages with personalized ( embeded password and id ) online link to a donation page ( https://secure.uwoakville.org/). we are relaying those emails using cogeco.ca smtp server.

We are not blacklisted.

Help!!!!.

Ewa

↧

blocked IP - 501 Connection rejected by policy [7.7] 17903

October 25, 2016, 12:08 pm

≫ Next: My server IP is blocked

≪ Previous: 5.1.0 - Unknown address error 553-'SPF

I need a solution

Dear Sir,

Dear Sirs and Madams,

We have checked our IP on http://ipremoval.sms.symantec.com/lookup/

and got answer as following

The IP address you submitted,

66.11.119.236
66.11.119.243

does not have a negative reputation and therefore cannot be submitted for investigation.

But we are still blocked and getting error "501 Connect Rejected by Policy [7.7]"

could you please remove our IPs from your blacklist.

66.11.119.236 -

66.11.119.243

Kind Regards

↧

My server IP is blocked

October 26, 2016, 9:03 pm

≫ Next: Quarantine Login Active Directory Integration

≪ Previous: blocked IP - 501 Connection rejected by policy [7.7] 17903

I need a solution

Hello,

Some weeks ago we had a situation with spam sending from our server with IP 209.133.193.86

The server was properly cleaned and we have restored our IP reputation,

Also we are currently not blacklisted in http://ipremoval.sms.symantec.com/lookup/

But we still receiving the following error message when sending to Symantec protected email servers.

LOG: MAIN
cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1bzPKT-00084x-BP
delivering 1bzPKT-00084x-BP
Connecting to cluster8.us.messagelabs.com [216.82.241.132]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.241.132] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.241.196]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.241.196] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.251.44]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.251.44] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.249.147]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.249.147] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.242.37]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.242.37] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.251.37]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.251.37] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.242.35]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.242.35] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.251.39]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.251.39] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.249.131]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.249.131] Connection timed out
Connecting to cluster8.us.messagelabs.com [216.82.242.45]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=cluster8.us.messagelabs.com [216.82.242.45] Connection timed out
Connecting to cluster8a.us.messagelabs.com [216.82.251.230]:25 ... failed: Connection refused

↧

Quarantine Login Active Directory Integration

October 27, 2016, 11:10 am

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

≪ Previous: My server IP is blocked

I need a solution

Hi,

We're looking at a pilot for email security cloud and one potential pitfall is that in our current solution (Brightmail), all our users are used to using their Active Directory login information to access their personal Quarantine.

Is it possible to integrate the sign-on for quarantine access in email security cloud with active directory, by either using SSO or password sync?

Thanks

↧

501 Connection rejected by policy [7.7] 17913

October 27, 2016, 12:31 pm

≫ Next: 501 Connection rejected

≪ Previous: Quarantine Login Active Directory Integration

I need a solution

Dear Symantec support team,

Our IP 104.28.16.65 has been blocked by some mail servers. This IP is fronted by Cloudflare service. Our main hosting IP is 85.25.78.183

We don't send any spam according to MX Toolbox report.

Please, help us to solve this.

Thank you!

↧

501 Connection rejected

November 1, 2016, 11:32 am

≫ Next: Symantec.cloud modifies Sender IP and causes SPF fail

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

I need a solution

Hello,

Our emails sent to our clients are getting filtered with delivery error "501 Connection rejected by policy [7.7]".

We don't have bad reputation :

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

Could you help me to check problem why our emails are blocked ?

WIth Best Regard

Omar T

1478119951

5052631

↧

Symantec.cloud modifies Sender IP and causes SPF fail

November 2, 2016, 4:40 am

≫ Next: How do clients learn about Service Alerts ?

≪ Previous: 501 Connection rejected

I need a solution

We have Symantec.Cloud on a number of sites and a potential issue has just been highlighted. A client of ours who does not use Symantec.Cloud (yet) has a valid SPF record setup and when he sends an e-mail to my personal Yahoo account it passes the SPF check with:

Received-SPF: pass (domain of cmauk.co.uk designates 209.85.217.181 as permitted sender)

However when he e-mails our work account it gets scanned by Symantec.Cloud and then passed on to our Office 365 setup and when it reached there the SPF fails:

Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
cmauk.co.uk discourages use of 195.245.230.39 as permitted sender)

Now as you can see the IP address has changed from 209.85.217.181 his Google IP to 195.245.230.39 a messagelabs IP and it fails the SPF check. It's not a big issue in our case as we can whitelist him but this must be happening to other clients all over the world where Messagelabs changes the IP and anything doing a SPF check behind it will cause a fail.

Is there anything that can be done to stop this change of IP address?

1478184400

↧

How do clients learn about Service Alerts ?

November 2, 2016, 12:59 pm

≫ Next: Connection rejected by policy [7.7] 4606

≪ Previous: Symantec.cloud modifies Sender IP and causes SPF fail

I need a solution

We use ClientNet > Support > Service Alerts to learn about various issues at Email Security.cloud.

However, we need to logon to ClientNet to see any new or updated items.

Some time ago we posted an idea that said -- the Service Alerts should be sent to clients via email.

How do other clients learn about new/changed Service Alerts ?

Do you logon to ClientNet "once per day" just to check on that ?

Thanks

======

1478187005

↧

Connection rejected by policy [7.7] 4606

November 4, 2016, 11:15 am

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

≪ Previous: How do clients learn about Service Alerts ?

I need a solution

Hello,

One of our clients is getting the following bounceback errors:

SMTP error from remote mail server after initial connection:

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

We have tried the blacklist removal tool availible here:

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

But does not seem to have helped. The IP address is 64.191.166.23

Let me know if there is anything we can do from our end to help get this removed.

Thanks

↧