Negative Reputation Repair

September 8, 2017, 9:42 am

≪ Previous: Messagelabs mail servers refuse the network connection

I need a solution

For some reason, my domains (all on the same server) have been blacklisted when sending emails sent to AT&T properties. Investigating the issue led me here, where I discovered the following about my IP:

The IP address 162.214.0.132 was found to have a negative reputation. Reasons for this assessment include:

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

I am not sure why/where this happened. What can I do to correct the problem?

↧

Message lab certificate

September 9, 2017, 9:17 am

≫ Next: mail blocked by messagelabs.com

≪ Previous: Negative Reputation Repair

I need a solution

Hi All,

One of our client using Symantec DLP deployed on premises and they also use Symantec.Cloud (formally known as message lab) for the email. Deployment of Email infra is as below:

sender user --> Exchange --> Symantec DLP --> Symantec.Cloud --> recepient user

In order to stablish TLS between Symantec DLP and .Cloud, we have to import .Cloud cert to the DLP Server keystore (requirement for the integration as per Symantec integration guide). We have already doesnloaded .Cloud cert and imported.

The Symantec.Cloud cert which we have imported, is set to expire in 2018. My question is, how shall we get to know when Symantec will be renewing Symantec.Cloud cert which we need to import to the DLP Server keystore manually. Can we get notification when new cert is available or any best practice?

Note: Symantec.Cloud cert need to be imported manually to the DLP Server keystore and if we didn;t import valid cert of Symantec.Cloud before it gets expired, Email flow will be intruppted.

Appriciate any input.

↧

mail blocked by messagelabs.com

September 11, 2017, 8:54 am

≫ Next: Problem sending email form our domain

≪ Previous: Message lab certificate

I need a solution

After changing internet provider we are unable to send emails to some of our clients. We are getting an error: "SMTP error from remote mail server after initial connection: host luster8.us.messagelabs.com: 501 Connection rejected by policy [7.7] xxxx, please visit www.messagelabs.com/support for more details about this error message"

I checked our IP address at http://ipremoval.sms.symantec.com/lookup and is not listed there.

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

I’ve already sent multiple requests to Investigation@review.symantec.com and haven’t received any reply.

Please help us to remove IP 64.191.36.74 from your blacklist.

Thanks!

↧

Problem sending email form our domain

September 12, 2017, 3:29 am

≫ Next: Cannot email MessageLabs protected domains

≪ Previous: mail blocked by messagelabs.com

I do not need a solution (just sharing information)

We have a problem sending email from our domain bulteck.com 176.31.3.43 to ferrovial.com under messagelabs.

The server sent properly the messages to messagelab servers, but the final user doesn't receive the email.

I attach a small report for one message sent this morning.

↧

Cannot email MessageLabs protected domains

September 12, 2017, 4:55 am

≫ Next: "501 Connection rejected by policy"

≪ Previous: Problem sending email form our domain

I need a solution

Hi,

We have a problem that started 2 days ago unexpectedly. I began getting reports from staff that certain clients of ours weren’t receiving emails from us.
On inspecting our mail logs I could see that the common factor between these clients was that they all use MessageLabs.

I've checked the reputation tool and can see that we do not have a negative reputation so am I bit stumped what’s going on. We could email perfectly fine at the start of the week?

Are there any other places I can check to see if MessageLabs have us on some kind of block list please?

Thanks

James

↧

"501 Connection rejected by policy"

September 12, 2017, 10:27 pm

≫ Next: Blacklist removal - messagelabs.com connection rejected by policy

≪ Previous: Cannot email MessageLabs protected domains

I need a solution

Hello!

We are a company offering various hosting services.

Recently, one customer have complained over Mail delivery failed: returning message to sender

Server ip 162.210.98.151 (deszr.com)

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 cluster1.eu.messagelabs.com<ht tp://cluster1.eu.messagelabs. com> [193.109.254.67]

SMTP error from remote mail server after initial connection:

501 Connection rejected by policy [7.7] 5608, please visit www.messagelabs.com/support< http://www.messagelabs.com/ support>

I would appreciate if anyone could help to this matter.

Thank you very much and good day.

↧

Blacklist removal - messagelabs.com connection rejected by policy

September 14, 2017, 10:52 am

≫ Next: SMTP session timing out but recipients still receiving emails?

≪ Previous: "501 Connection rejected by policy"

I need a solution

Hello Symantec team!

We recently identified a bug in one of our clients that was infected by a malicious script that started firing several spam.

We have solved the problem, but note that some outgoing emails are being blocked.

I searched our main IP for investigation at (http://ipremoval.sms.symantec.com/lookup/) and there is no blocking, even though they are getting the following error:

Delivery Host: cluster5.us.messagelabs.com

SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 12606, please visit www.messagelabs.com/support for more details about this error message.

Our main shipping IP is:
204.12.202.18

And the other IPs we also use:
204.12.202.19
204.12.202.20
204.12.202.21

I thank you for your help.

↧

SMTP session timing out but recipients still receiving emails?

September 15, 2017, 4:35 am

≫ Next: Sending Mails to @de.dsv.com is not possible

≪ Previous: Blacklist removal - messagelabs.com connection rejected by policy

I need a solution

Hi Symantec,

We operate a cloud-based SaaS service which allows our users to manage marketing emails to their customers.

We have been finding that several recipients have been receiving multiple copies of email sent out, and upon investigating from our end, the connection to the messagelabs.com servers are either refusing connection, or simply timing out. That wouldn't necessarily be a problem as our mail server will simply mark the email as 'bounced', however, it would appear that the recipients are actually receiving some (if not all) of these emails.

You can see from a log extract below that our mail server attempts to connect to many different servers of yours and each one exhibits a similar problem. In many cases, even though it claims to accept the message, the session simply times out after 60 seconds, thus resulting in another retry.

I have checked that our outbound IP (in this case 46.37.186.167) is not listed on your blocklist (http://ipremoval.sms.symantec.com/lookup/).

Log extract:

[2017.09.12] 11:34:04 [11411] Sending remote mail for bounce-10-1259-6749-6638686-177@clarity-marketing.com
[2017.09.12] 11:34:04 [11411] Initiating connection to 216.82.242.34
[2017.09.12] 11:34:04 [11411] Connecting to 216.82.242.34:25 (Id: 1)
[2017.09.12] 11:34:04 [11411] Binding to local IP 172.27.226.13:0 (Id: 1)
[2017.09.12] 11:34:04 [11411] Connection to 216.82.242.34:25 from 172.27.226.13:55517 succeeded (Id: 1)
[2017.09.12] 11:34:04 [11411] RSP: 220 ***************************************
[2017.09.12] 11:34:04 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:34:04 [11411] RSP: 250-server-9.tower-73.messagelabs.com
[2017.09.12] 11:34:04 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:34:04 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:34:04 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:34:04 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:34:04 [11411] RSP: 250 OK
[2017.09.12] 11:34:04 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:34:05 [11411] RSP: 250 OK
[2017.09.12] 11:34:05 [11411] CMD: DATA
[2017.09.12] 11:34:05 [11411] RSP: 354 go ahead
[2017.09.12] 11:35:05 [11411] The smtp session has timed out.
[2017.09.12] 11:35:05 [11411] Initiating connection to 216.82.251.37
[2017.09.12] 11:35:05 [11411] Connecting to 216.82.251.37:25 (Id: 2)
[2017.09.12] 11:35:05 [11411] Binding to local IP 172.27.226.13:0 (Id: 2)
[2017.09.12] 11:35:05 [11411] Connection to 216.82.251.37:25 from 172.27.226.13:55773 succeeded (Id: 2)
[2017.09.12] 11:35:05 [11411] RSP: 220 ****************************************
[2017.09.12] 11:35:05 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:35:05 [11411] RSP: 250-server-3.tower-153.messagelabs.com
[2017.09.12] 11:35:05 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:35:05 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:35:05 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:35:05 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:35:05 [11411] RSP: 250 OK
[2017.09.12] 11:35:05 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:35:06 [11411] RSP: 250 OK
[2017.09.12] 11:35:06 [11411] CMD: DATA
[2017.09.12] 11:35:06 [11411] RSP: 354 go ahead
[2017.09.12] 11:36:06 [11411] The smtp session has timed out.
[2017.09.12] 11:36:06 [11411] Initiating connection to 216.82.242.37
[2017.09.12] 11:36:06 [11411] Connecting to 216.82.242.37:25 (Id: 3)
[2017.09.12] 11:36:06 [11411] Binding to local IP 172.27.226.13:0 (Id: 3)
[2017.09.12] 11:36:06 [11411] Connection to 216.82.242.37:25 from 172.27.226.13:56185 succeeded (Id: 3)
[2017.09.12] 11:36:06 [11411] RSP: 220 ****************************************
[2017.09.12] 11:36:06 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:36:06 [11411] RSP: 250-server-16.tower-99.messagelabs.com
[2017.09.12] 11:36:06 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:36:06 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:36:06 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:36:06 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:36:06 [11411] RSP: 250 OK
[2017.09.12] 11:36:06 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:36:06 [11411] RSP: 250 OK
[2017.09.12] 11:36:06 [11411] CMD: DATA
[2017.09.12] 11:36:07 [11411] RSP: 354 go ahead
[2017.09.12] 11:37:07 [11411] The smtp session has timed out.
[2017.09.12] 11:37:07 [11411] Initiating connection to 216.82.250.51
[2017.09.12] 11:37:07 [11411] Connecting to 216.82.250.51:25 (Id: 4)
[2017.09.12] 11:37:07 [11411] Binding to local IP 172.27.226.13:0 (Id: 4)
[2017.09.12] 11:37:07 [11411] Connection to 216.82.250.51:25 from 172.27.226.13:56510 succeeded (Id: 4)
[2017.09.12] 11:37:07 [11411] RSP: 220 *****************************************
[2017.09.12] 11:37:07 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:37:07 [11411] RSP: 250-server-13.tower-108.messagelabs.com
[2017.09.12] 11:37:07 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:37:07 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:37:07 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:37:07 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:37:07 [11411] RSP: 250 OK
[2017.09.12] 11:37:07 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:37:08 [11411] RSP: 250 OK
[2017.09.12] 11:37:08 [11411] CMD: DATA
[2017.09.12] 11:37:08 [11411] RSP: 354 go ahead
[2017.09.12] 11:38:08 [11411] The smtp session has timed out.
[2017.09.12] 11:38:08 [11411] Initiating connection to 216.82.242.131
[2017.09.12] 11:38:08 [11411] Connecting to 216.82.242.131:25 (Id: 5)
[2017.09.12] 11:38:08 [11411] Binding to local IP 172.27.226.13:0 (Id: 5)
[2017.09.12] 11:38:09 [11411] Exception connecting to 216.82.242.131 (Id: 5)
[2017.09.12] 11:38:09 [11411] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 216.82.242.131:25
[2017.09.12] 11:38:09 [11411] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.
[2017.09.12] 11:38:09 [11411] Connecting to 216.82.242.131:25 (Id: 6)
[2017.09.12] 11:38:09 [11411] Connection to 216.82.242.131:25 from 172.27.226.9:56821 succeeded (Id: 6)
[2017.09.12] 11:38:09 [11411] RSP: 220 ***************************************
[2017.09.12] 11:38:09 [11411] CMD: EHLO mail.claritygo.com
[2017.09.12] 11:38:10 [11411] RSP: 250-server-6.tower-76.messagelabs.com
[2017.09.12] 11:38:10 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:38:10 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:38:10 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:38:10 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:38:10 [11411] RSP: 250 OK
[2017.09.12] 11:38:10 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:38:10 [11411] RSP: 250 OK
[2017.09.12] 11:38:10 [11411] CMD: DATA
[2017.09.12] 11:38:10 [11411] RSP: 354 go ahead
[2017.09.12] 11:39:10 [11411] The smtp session has timed out.
[2017.09.12] 11:39:10 [11411] Initiating connection to 216.82.241.195
[2017.09.12] 11:39:10 [11411] Connecting to 216.82.241.195:25 (Id: 7)
[2017.09.12] 11:39:10 [11411] Binding to local IP 172.27.226.13:0 (Id: 7)
[2017.09.12] 11:39:10 [11411] Connection to 216.82.241.195:25 from 172.27.226.13:57076 succeeded (Id: 7)
[2017.09.12] 11:39:10 [11411] RSP: 220 *****************************************
[2017.09.12] 11:39:10 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:39:10 [11411] RSP: 250-server-10.tower-119.messagelabs.com
[2017.09.12] 11:39:10 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:39:10 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:39:10 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:39:10 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:39:11 [11411] RSP: 250 OK
[2017.09.12] 11:39:11 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:39:11 [11411] RSP: 250 OK
[2017.09.12] 11:39:11 [11411] CMD: DATA
[2017.09.12] 11:39:11 [11411] RSP: 354 go ahead
[2017.09.12] 11:40:11 [11411] The smtp session has timed out.
[2017.09.12] 11:40:11 [11411] Initiating connection to 216.82.250.83
[2017.09.12] 11:40:11 [11411] Connecting to 216.82.250.83:25 (Id: 8)
[2017.09.12] 11:40:11 [11411] Binding to local IP 172.27.226.13:0 (Id: 8)
[2017.09.12] 11:40:11 [11411] Connection to 216.82.250.83:25 from 172.27.226.13:57383 succeeded (Id: 8)
[2017.09.12] 11:40:11 [11411] RSP: 220 ****************************************
[2017.09.12] 11:40:11 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:40:11 [11411] RSP: 250-server-5.tower-120.messagelabs.com
[2017.09.12] 11:40:11 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:40:11 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:40:11 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:40:11 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:40:12 [11411] RSP: 250 OK
[2017.09.12] 11:40:12 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:40:12 [11411] RSP: 250 OK
[2017.09.12] 11:40:12 [11411] CMD: DATA
[2017.09.12] 11:40:12 [11411] RSP: 354 go ahead
[2017.09.12] 11:41:12 [11411] The smtp session has timed out.
[2017.09.12] 11:41:12 [11411] Initiating connection to 216.82.251.35
[2017.09.12] 11:41:12 [11411] Connecting to 216.82.251.35:25 (Id: 9)
[2017.09.12] 11:41:12 [11411] Binding to local IP 172.27.226.13:0 (Id: 9)
[2017.09.12] 11:41:12 [11411] Connection to 216.82.251.35:25 from 172.27.226.13:57665 succeeded (Id: 9)
[2017.09.12] 11:41:12 [11411] RSP: 220 ****************************************
[2017.09.12] 11:41:12 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:41:13 [11411] RSP: 250-server-3.tower-151.messagelabs.com
[2017.09.12] 11:41:13 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:41:13 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:41:13 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:41:13 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:41:13 [11411] RSP: 250 OK
[2017.09.12] 11:41:13 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:41:13 [11411] RSP: 250 OK
[2017.09.12] 11:41:13 [11411] CMD: DATA
[2017.09.12] 11:41:13 [11411] RSP: 354 go ahead
[2017.09.12] 11:42:13 [11411] The smtp session has timed out.
[2017.09.12] 11:42:13 [11411] Initiating connection to 216.82.250.99
[2017.09.12] 11:42:13 [11411] Connecting to 216.82.250.99:25 (Id: 10)
[2017.09.12] 11:42:13 [11411] Binding to local IP 172.27.226.13:0 (Id: 10)
[2017.09.12] 11:42:14 [11411] Connection to 216.82.250.99:25 from 172.27.226.13:57915 succeeded (Id: 10)
[2017.09.12] 11:42:14 [11411] RSP: 220 ****************************************
[2017.09.12] 11:42:14 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:42:14 [11411] RSP: 250-server-7.tower-126.messagelabs.com
[2017.09.12] 11:42:14 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:42:14 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:42:14 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:42:14 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:42:14 [11411] RSP: 250 OK
[2017.09.12] 11:42:14 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:42:14 [11411] RSP: 250 OK
[2017.09.12] 11:42:14 [11411] CMD: DATA
[2017.09.12] 11:42:14 [11411] RSP: 354 go ahead
[2017.09.12] 11:43:15 [11411] The smtp session has timed out.
[2017.09.12] 11:43:15 [11411] Initiating connection to 216.82.251.36
[2017.09.12] 11:43:15 [11411] Connecting to 216.82.251.36:25 (Id: 11)
[2017.09.12] 11:43:15 [11411] Binding to local IP 172.27.226.13:0 (Id: 11)
[2017.09.12] 11:43:15 [11411] Connection to 216.82.251.36:25 from 172.27.226.13:58223 succeeded (Id: 11)
[2017.09.12] 11:43:15 [11411] RSP: 220 ****************************************
[2017.09.12] 11:43:15 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:43:15 [11411] RSP: 250-server-8.tower-152.messagelabs.com
[2017.09.12] 11:43:15 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:43:15 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:43:15 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:43:15 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:43:15 [11411] RSP: 250 OK
[2017.09.12] 11:43:15 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:43:15 [11411] RSP: 250 OK
[2017.09.12] 11:43:15 [11411] CMD: DATA
[2017.09.12] 11:43:16 [11411] RSP: 354 go ahead
[2017.09.12] 11:44:16 [11411] The smtp session has timed out.
[2017.09.12] 11:44:16 [11411] Initiating connection to 216.82.242.147
[2017.09.12] 11:44:16 [11411] Connecting to 216.82.242.147:25 (Id: 12)
[2017.09.12] 11:44:16 [11411] Binding to local IP 172.27.226.13:0 (Id: 12)
[2017.09.12] 11:44:16 [11411] Connection to 216.82.242.147:25 from 172.27.226.13:58495 succeeded (Id: 12)
[2017.09.12] 11:44:16 [11411] RSP: 220 ****************************************
[2017.09.12] 11:44:16 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:44:16 [11411] RSP: 250-server-11.tower-95.messagelabs.com
[2017.09.12] 11:44:16 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:44:16 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:44:16 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:44:16 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:44:16 [11411] RSP: 250 OK
[2017.09.12] 11:44:16 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:44:16 [11411] RSP: 250 OK
[2017.09.12] 11:44:16 [11411] CMD: DATA
[2017.09.12] 11:44:17 [11411] RSP: 354 go ahead
[2017.09.12] 11:45:17 [11411] The smtp session has timed out.
[2017.09.12] 11:45:17 [11411] Initiating connection to 216.82.251.230
[2017.09.12] 11:45:17 [11411] Connecting to 216.82.251.230:25 (Id: 13)
[2017.09.12] 11:45:17 [11411] Binding to local IP 172.27.226.13:0 (Id: 13)
[2017.09.12] 11:45:17 [11411] Connection to 216.82.251.230:25 from 172.27.226.13:58756 succeeded (Id: 13)
[2017.09.12] 11:45:17 [11411] RSP: 220 *****************************************
[2017.09.12] 11:45:17 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:45:18 [11411] RSP: 250-server-12.tower-555.messagelabs.com says EHLO to 46.37.186.167:58756
[2017.09.12] 11:45:18 [11411] RSP: 250-8BITMIME
[2017.09.12] 11:45:18 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:45:18 [11411] RSP: 250 PIPELINING
[2017.09.12] 11:45:18 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:45:18 [11411] RSP: 250 2.0.0 MAIL FROM accepted
[2017.09.12] 11:45:18 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:45:18 [11411] RSP: 421 Service Temporarily Unavailable
[2017.09.12] 11:45:18 [11411] CMD: QUIT

↧

Sending Mails to @de.dsv.com is not possible

September 15, 2017, 7:29 am

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

≪ Previous: SMTP session timing out but recipients still receiving emails?

I need a solution

Dear Support,

I've a Mailserver and i receive the following in my Logfile.

Cause your Mailcluster dosn't tell me a reason why, i don't know why.

--->

Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4a.eu.messagelabs.com[85.158.139.103]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12582]: F3D2AA0E28: to=<palettenabteilung.aschaffenburg@de.dsv.com>, relay=none, delay=372286, delays=372136/0.02/150/0, dsn=4.4.1, status=deferred (connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out)

<--

Regards

Markus Lembke

↧

501 Connection rejected by policy [7.7] 20611

September 19, 2017, 12:03 am

≫ Next: MessageLabs mail flow rule

≪ Previous: Sending Mails to @de.dsv.com is not possible

I do not need a solution (just sharing information)

Hi there ...

Im got this error from one of my clients, that apperently cant sent emails to his reciever. Maybe u can see the problem ?

MailEnable: Message Delivery Failure.

Reason: ME-E0193: [A9E55067186948C4AFC8193A6EB6A975.MAI] Message Delivery Failure.

Your message addressed to the target domain (faarup.dk) could not be delivered because the mail server responsible for this domain returned a permanent error.

The server returned:

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

Message headers follow:

Received: from DESKTOPL45HMO9 ([90.185.116.210]) by architection.net with MailEnable ESMTPA; Tue, 19 Sep 2017 08:07:10 +0200

↧

MessageLabs mail flow rule

September 19, 2017, 4:08 am

≫ Next: Blacklist removal - protection.your-mailbox.eu connection rejected by policy

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

I need a solution

Hi,

Where in MessageLabs would a person find the settings to:

* Ignore an email domains DNS MX records

* Send directly to another destination such as Office 365 for a specific domain

Now, before everyone goes off their nu...I don't actually want to do this. I'm not crazy, but I need to know where in MessageLabs I would do this so I can tell a 3rd party partner (that is crazy) where to remove this setting (which they refuse to acknowledge they have configured).

Thank you.

↧

Blacklist removal - protection.your-mailbox.eu connection rejected by policy

September 19, 2017, 4:45 am

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

≪ Previous: MessageLabs mail flow rule

I do not need a solution (just sharing information)

Hello Symantec team!

Since Settembre 15, 2017, we changed our server provider and we did the installation server from scratch and migrated our services to the newly adquired server/IP.

We are asking you the posibility to make a new evaluation to this IP group, because our mails clients are being rejected.

The IP are:
193.70.107.39
193.70.107.40
193.70.107.41
193.70.107.42
193.70.107.43
193.70.107.48
193.70.107.49
193.70.107.50
193.70.107.51
193.70.107.52

LOG

Sep 19 08:31:09 protection klms-smtp_proxy: Message from <*****@bergaminiroberto.it> to <*****@alice.it> passed
Sep 19 08:31:09 protection postfix/smtpd[11501]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 Ok: queued as DE310FFBC4; from=<*****@bergaminiroberto.it> to=<*****@alice.it> proto=ESMTP helo=<smtpauth.your-mailbox.eu>
Sep 19 08:31:10 protection postfix/smtp[11492]: DE310FFBC4: to=<******@alice.it>, relay=smtp.aliceposta.it[82.57.200.133]:25, delay=0.22, delays=0.06/0/0.09/0.07, dsn=5.0.0, status=bounced (host smtp.aliceposta.it[82.57.200.133] said: 550 mail not accepted from blacklisted IP address [193.70.107.48] (in reply to MAIL FROM command))

Thanks for your time and help, please let me know if you need something else.

↧

501 Connection rejected by policy [7.7] 13007

September 20, 2017, 10:33 am

≫ Next: Removal request

≪ Previous: Blacklist removal - protection.your-mailbox.eu connection rejected by policy

I need a solution

Greetings,

I have my own VPS and clients who uses it as email server, I have been blacklisted with the following IPs:

193.109.69.177

193.109.69.182

193.109.69.185

this is the letter I get when trying to send emails:

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:
support.cloud@symantec.com
    host cluster4.us.messagelabs.com [216.82.251.33]
    SMTP error from remote mail server after initial connection:
    501 Connection rejected by policy [7.7] 13007, please visit www.messagelabs.com/support for more details about this error message.

Hope it can be sloved soon.

best regards.

↧

Removal request

September 21, 2017, 6:49 am

≫ Next: connect to clusterxx.us.messagelabs.com...Connection refused

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

I need a solution

Hello support !

I would like to ask you to check if your mail server are blocking our IP addresses. When trying to connect to your servers I get timeout :

telnet cluster1.eu.messagelabs.com 25
Trying 85.158.136.67...
telnet: connect to address 85.158.136.67: Connection timed out

The IP of our server is 148.251.152.171

Could you check ?

thank you in advance

Andrzej Zielinski

↧

connect to clusterxx.us.messagelabs.com...Connection refused

September 21, 2017, 7:03 am

≫ Next: 501 Connection rejected by policy [7.7] 20604 IPs ALL Clean URGENT

≪ Previous: Removal request

I need a solution

I haven't needed to email many people behind Symantec 'messagelabs' protection, but this 'connection refused' issue has come up again, so I'm checking it out further.

My mail server was assigned a new public IP address (74.117.210.6) some time back and I've been unable to email 'messagelabs' recipients since.

I've checked the lookup tool (http://ipremoval.sms.symantec.com/lookup/) against my mail server IP and it came back clean.

My situation seems very simlar to this one where an *internal* list at Symantec was involved:
https://www.symantec.com/connect/forums/connect-cl...

↧

501 Connection rejected by policy [7.7] 20604 IPs ALL Clean URGENT

September 21, 2017, 8:02 am

≫ Next: Emails to messagelabs customers being blocked with 553 Message filtered

≪ Previous: connect to clusterxx.us.messagelabs.com...Connection refused

I need a solution

Hi,

I already check http://ipremoval.sms.symantec.com/lookup/, but my IPs does not have a negative reputation. I have a client waiting for my service proposal
and he does not receive my email.

MY IPs
64.187.229.179
64.187.229.180
64.187.229.181

Bruno

2017-09-21 11:36:05 1dv2aA-0005AW-AO ** XXXXXXXXXXXX R=dkim_lookuphost T=dkim_remote_smtp H=cluster4.eu.messagelabs.com [85.158.139.211]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 20604, please visit www.messagelabs.com/support for more details about this error message.
2017-09-21 11:36:05 1dv2aA-0005AW-AO ** XXXXXXXXXXXXXX R=dkim_lookuphost T=dkim_remote_smtp H=cluster4.eu.messagelabs.com [85.158.139.211]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 20604, please visit www.messagelabs.com/support for more details about this error message.

↧

Emails to messagelabs customers being blocked with 553 Message filtered

September 21, 2017, 8:39 am

≫ Next: Emails being blocked by massagelabs

≪ Previous: 501 Connection rejected by policy [7.7] 20604 IPs ALL Clean URGENT

I need a solution

Hello,

In the last few days all of our corporate emails to certain clients are being blocked, with the same response:

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

We have checked against the troubleshooting page and cannot see anything wrong. We have a suspicion that it may be due to a recent change for one of our clients where we routed the emails being sent from the platform we provide them through messagelabs. Each email sent was also being BCC'd to one of our email address for auditing purposes, and we wonder if this has flagged something up at your end? We have reversed this now.

I have emailed investigation@review.symantec.com with more info, but we also thought we would try here in case we get a faster response as it's causing us a number of problems.

Any help would be very much appreciated!

Regards,

Nathan.

↧

Emails being blocked by massagelabs

September 21, 2017, 4:27 pm

≫ Next: Emails to clients using your service seem to be blocked from our Mail Server with a new ip 210.8.160.250 which is mail.barkerbp.com How can we have it delisted?

≪ Previous: Emails to messagelabs customers being blocked with 553 Message filtered

I need a solution

Hello.

The IP of my Dedicated Server is being blocked in e-mail submissions to recipients using messagelabs

My Server IP is 216.245.210.218

Hostname is server.brzoom.com.br

See this:

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:

Enos.SOARES@danone.com
host cluster5.eu.messagelabs.com [85.158.138.179]
SMTP error from remote mail server after initial connection:
501 Connection rejected by policy [7.7] 16909, please visit www.messagelabs.com/support for more details about this error message.

Also, see image attached, please.

Plese, check it for me.

Thank you for helping me.

messagelabs.jpeg

↧

Emails to clients using your service seem to be blocked from our Mail Server with a new ip 210.8.160.250 which is mail.barkerbp.com How can we have it delisted?

September 21, 2017, 10:31 pm

≫ Next: 421 response despite mail being delivered

≪ Previous: Emails being blocked by massagelabs

I need a solution

↧

421 response despite mail being delivered

September 22, 2017, 3:53 am

≫ Next: Require Messagelabs IP source IP range (mail1.bemta5.messagelabs.com)

≪ Previous: Emails to clients using your service seem to be blocked from our Mail Server with a new ip 210.8.160.250 which is mail.barkerbp.com How can we have it delisted?

I need a solution

Hi Symantec,

We operate a cloud-based SaaS service which allows our users to manage marketing emails to their customers.

This is in follow-up to a previous issue, which I believe is now resolved as you have removed us from your throttling.

However, we are now receiving connection timeouts and a 421 response when we can connect. Again, this isn't necessarily a problem, but it would appear that the email is still being delivered to the recipient. Log extract is below.

Can you advise on what this 421 refers to and how we should handle this?

Thanks in advance
David

Log Extract:

[2017.09.22] 06:17:05 [26127] Delivery started for bounce-10-1259-6751-6502204-177@clarity-marketing.com at 06:17:05

[2017.09.22] 06:17:08 [26127] Skipping spam checks: No local recipients

[2017.09.22] 06:17:11 [26127] Sending remote mail for bounce-10-1259-6751-6502204-177@clarity-marketing.com

[2017.09.22] 06:17:11 [26127] Initiating connection to 85.158.143.35

[2017.09.22] 06:17:11 [26127] Connecting to 85.158.143.35:25 (Id: 1)

[2017.09.22] 06:17:11 [26127] Binding to local IP 172.27.226.13:0 (Id: 1)

[2017.09.22] 06:17:32 [26127] Exception connecting to 85.158.143.35 (Id: 1)

[2017.09.22] 06:17:32 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 06:17:32 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 06:17:32 [26127] Connecting to 85.158.143.35:25 (Id: 2)

[2017.09.22] 06:17:53 [26127] Exception connecting to 85.158.143.35 (Id: 2)

[2017.09.22] 06:17:53 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 06:17:53 [26127] Connection to 85.158.143.35 failed (Id: 2)

[2017.09.22] 06:17:53 [26127] Initiating connection to 193.109.254.147

[2017.09.22] 06:17:53 [26127] Connecting to 193.109.254.147:25 (Id: 3)

[2017.09.22] 06:17:53 [26127] Binding to local IP 172.27.226.13:0 (Id: 3)

[2017.09.22] 06:17:56 [26127] Exception connecting to 193.109.254.147 (Id: 3)

[2017.09.22] 06:17:56 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 193.109.254.147:25

[2017.09.22] 06:17:56 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 06:17:56 [26127] Connecting to 193.109.254.147:25 (Id: 4)

[2017.09.22] 06:18:17 [26127] Exception connecting to 193.109.254.147 (Id: 4)

[2017.09.22] 06:18:17 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 193.109.254.147:25

[2017.09.22] 06:18:17 [26127] Connection to 193.109.254.147 failed (Id: 4)

[2017.09.22] 06:18:17 [26127] Initiating connection to 85.158.139.211

[2017.09.22] 06:18:17 [26127] Connecting to 85.158.139.211:25 (Id: 5)

[2017.09.22] 06:18:17 [26127] Binding to local IP 172.27.226.13:0 (Id: 5)

[2017.09.22] 06:18:38 [26127] Exception connecting to 85.158.139.211 (Id: 5)

[2017.09.22] 06:18:38 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.211:25

[2017.09.22] 06:18:38 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 06:18:38 [26127] Connecting to 85.158.139.211:25 (Id: 6)

[2017.09.22] 06:18:59 [26127] Exception connecting to 85.158.139.211 (Id: 6)

[2017.09.22] 06:18:59 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.211:25

[2017.09.22] 06:18:59 [26127] Connection to 85.158.139.211 failed (Id: 6)

[2017.09.22] 06:18:59 [26127] Initiating connection to 85.158.137.68

[2017.09.22] 06:18:59 [26127] Connecting to 85.158.137.68:25 (Id: 7)

[2017.09.22] 06:18:59 [26127] Binding to local IP 172.27.226.13:0 (Id: 7)

[2017.09.22] 06:19:01 [26127] Exception connecting to 85.158.137.68 (Id: 7)

[2017.09.22] 06:19:01 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 85.158.137.68:25

[2017.09.22] 06:19:01 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 06:19:01 [26127] Connecting to 85.158.137.68:25 (Id: 8)

[2017.09.22] 06:19:22 [26127] Exception connecting to 85.158.137.68 (Id: 8)

[2017.09.22] 06:19:22 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.137.68:25

[2017.09.22] 06:19:22 [26127] Connection to 85.158.137.68 failed (Id: 8)

[2017.09.22] 06:19:22 [26127] Initiating connection to 85.158.139.103

[2017.09.22] 06:19:22 [26127] Connecting to 85.158.139.103:25 (Id: 9)

[2017.09.22] 06:19:22 [26127] Binding to local IP 172.27.226.13:0 (Id: 9)

[2017.09.22] 06:19:43 [26127] Exception connecting to 85.158.139.103 (Id: 9)

[2017.09.22] 06:19:43 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.103:25

[2017.09.22] 06:19:43 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 06:19:43 [26127] Connecting to 85.158.139.103:25 (Id: 10)

[2017.09.22] 06:20:04 [26127] Exception connecting to 85.158.139.103 (Id: 10)

[2017.09.22] 06:20:04 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.103:25

[2017.09.22] 06:20:04 [26127] Connection to 85.158.139.103 failed (Id: 10)

[2017.09.22] 06:20:04 [26127] Initiating connection to 216.82.251.230

[2017.09.22] 06:20:04 [26127] Connecting to 216.82.251.230:25 (Id: 11)

[2017.09.22] 06:20:04 [26127] Binding to local IP 172.27.226.13:0 (Id: 11)

[2017.09.22] 06:20:04 [26127] Connection to 216.82.251.230:25 from 172.27.226.13:59690 succeeded (Id: 11)

[2017.09.22] 06:20:04 [26127] RSP: 220 *****************************************

[2017.09.22] 06:20:04 [26127] CMD: EHLO mail3.claritygo.com

[2017.09.22] 06:20:05 [26127] RSP: 250-server-11.tower-555.messagelabs.com says EHLO to 46.37.186.167:59690

[2017.09.22] 06:20:05 [26127] RSP: 250-8BITMIME

[2017.09.22] 06:20:05 [26127] RSP: 250-XXXXXXXA

[2017.09.22] 06:20:05 [26127] RSP: 250 PIPELINING

[2017.09.22] 06:20:05 [26127] CMD: MAIL FROM:<bounce-10-1259-6751-6502204-177@clarity-marketing.com>

[2017.09.22] 06:20:05 [26127] RSP: 250 2.0.0 MAIL FROM accepted

[2017.09.22] 06:20:05 [26127] CMD: RCPT TO:<jessica.barrett@principleglobal.com>

[2017.09.22] 06:20:05 [26127] RSP: 421 Service Temporarily Unavailable

[2017.09.22] 06:20:05 [26127] CMD: QUIT

[2017.09.22] 07:20:12 [26127] Sending remote mail for bounce-10-1259-6751-6502204-177@clarity-marketing.com

[2017.09.22] 07:20:12 [26127] Initiating connection to 85.158.143.35

[2017.09.22] 07:20:12 [26127] Connecting to 85.158.143.35:25 (Id: 1)

[2017.09.22] 07:20:12 [26127] Binding to local IP 172.27.226.13:0 (Id: 1)

[2017.09.22] 07:20:33 [26127] Exception connecting to 85.158.143.35 (Id: 1)

[2017.09.22] 07:20:33 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 07:20:33 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 07:20:33 [26127] Connecting to 85.158.143.35:25 (Id: 2)

[2017.09.22] 07:20:54 [26127] Exception connecting to 85.158.143.35 (Id: 2)

[2017.09.22] 07:20:54 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 07:20:54 [26127] Connection to 85.158.143.35 failed (Id: 2)

[2017.09.22] 07:20:54 [26127] Initiating connection to 85.158.137.68

[2017.09.22] 07:20:54 [26127] Connecting to 85.158.137.68:25 (Id: 3)

[2017.09.22] 07:20:54 [26127] Binding to local IP 172.27.226.13:0 (Id: 3)

[2017.09.22] 07:20:55 [26127] Exception connecting to 85.158.137.68 (Id: 3)

[2017.09.22] 07:20:55 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 85.158.137.68:25

[2017.09.22] 07:20:55 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 07:20:55 [26127] Connecting to 85.158.137.68:25 (Id: 4)

[2017.09.22] 07:21:16 [26127] Exception connecting to 85.158.137.68 (Id: 4)

[2017.09.22] 07:21:16 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.137.68:25

[2017.09.22] 07:21:16 [26127] Connection to 85.158.137.68 failed (Id: 4)

[2017.09.22] 07:21:16 [26127] Initiating connection to 85.158.139.211

[2017.09.22] 07:21:16 [26127] Connecting to 85.158.139.211:25 (Id: 5)

[2017.09.22] 07:21:16 [26127] Binding to local IP 172.27.226.13:0 (Id: 5)

[2017.09.22] 07:21:17 [26127] Exception connecting to 85.158.139.211 (Id: 5)

[2017.09.22] 07:21:17 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 85.158.139.211:25

[2017.09.22] 07:21:17 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 07:21:17 [26127] Connecting to 85.158.139.211:25 (Id: 6)

[2017.09.22] 07:21:38 [26127] Exception connecting to 85.158.139.211 (Id: 6)

[2017.09.22] 07:21:38 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.211:25

[2017.09.22] 07:21:38 [26127] Connection to 85.158.139.211 failed (Id: 6)

[2017.09.22] 07:21:38 [26127] Initiating connection to 193.109.254.147

[2017.09.22] 07:21:38 [26127] Connecting to 193.109.254.147:25 (Id: 7)

[2017.09.22] 07:21:38 [26127] Binding to local IP 172.27.226.13:0 (Id: 7)

[2017.09.22] 07:21:59 [26127] Exception connecting to 193.109.254.147 (Id: 7)

[2017.09.22] 07:21:59 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 193.109.254.147:25

[2017.09.22] 07:21:59 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 07:21:59 [26127] Connecting to 193.109.254.147:25 (Id: 8)

[2017.09.22] 07:22:20 [26127] Exception connecting to 193.109.254.147 (Id: 8)

[2017.09.22] 07:22:20 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 193.109.254.147:25

[2017.09.22] 07:22:20 [26127] Connection to 193.109.254.147 failed (Id: 8)

[2017.09.22] 07:22:20 [26127] Initiating connection to 85.158.139.103

[2017.09.22] 07:22:20 [26127] Connecting to 85.158.139.103:25 (Id: 9)

[2017.09.22] 07:22:20 [26127] Binding to local IP 172.27.226.13:0 (Id: 9)

[2017.09.22] 07:22:21 [26127] Exception connecting to 85.158.139.103 (Id: 9)

[2017.09.22] 07:22:21 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 85.158.139.103:25

[2017.09.22] 07:22:21 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 07:22:21 [26127] Connecting to 85.158.139.103:25 (Id: 10)

[2017.09.22] 07:22:43 [26127] Exception connecting to 85.158.139.103 (Id: 10)

[2017.09.22] 07:22:43 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.103:25

[2017.09.22] 07:22:43 [26127] Connection to 85.158.139.103 failed (Id: 10)

[2017.09.22] 07:22:43 [26127] Initiating connection to 216.82.251.230

[2017.09.22] 07:22:43 [26127] Connecting to 216.82.251.230:25 (Id: 11)

[2017.09.22] 07:22:43 [26127] Binding to local IP 172.27.226.13:0 (Id: 11)

[2017.09.22] 07:22:43 [26127] Connection to 216.82.251.230:25 from 172.27.226.13:63750 succeeded (Id: 11)

[2017.09.22] 07:22:43 [26127] RSP: 220 *****************************************

[2017.09.22] 07:22:43 [26127] CMD: EHLO mail3.claritygo.com

[2017.09.22] 07:22:43 [26127] RSP: 250-server-11.tower-555.messagelabs.com says EHLO to 46.37.186.167:63750

[2017.09.22] 07:22:43 [26127] RSP: 250-XXXXXXXA

[2017.09.22] 07:22:43 [26127] RSP: 250-PIPELINING

[2017.09.22] 07:22:43 [26127] RSP: 250 8BITMIME

[2017.09.22] 07:22:43 [26127] CMD: MAIL FROM:<bounce-10-1259-6751-6502204-177@clarity-marketing.com>

[2017.09.22] 07:22:44 [26127] RSP: 250 2.0.0 MAIL FROM accepted

[2017.09.22] 07:22:44 [26127] CMD: RCPT TO:<jessica.barrett@principleglobal.com>

[2017.09.22] 07:22:44 [26127] RSP: 421 Service Temporarily Unavailable

[2017.09.22] 07:22:44 [26127] CMD: QUIT

[2017.09.22] 08:22:49 [26127] Sending remote mail for bounce-10-1259-6751-6502204-177@clarity-marketing.com

[2017.09.22] 08:22:49 [26127] Initiating connection to 85.158.139.211

[2017.09.22] 08:22:49 [26127] Connecting to 85.158.139.211:25 (Id: 1)

[2017.09.22] 08:22:49 [26127] Binding to local IP 172.27.226.13:0 (Id: 1)

[2017.09.22] 08:23:10 [26127] Exception connecting to 85.158.139.211 (Id: 1)

[2017.09.22] 08:23:10 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.211:25

[2017.09.22] 08:23:10 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 08:23:10 [26127] Connecting to 85.158.139.211:25 (Id: 2)

[2017.09.22] 08:23:31 [26127] Exception connecting to 85.158.139.211 (Id: 2)

[2017.09.22] 08:23:31 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.139.211:25

[2017.09.22] 08:23:31 [26127] Connection to 85.158.139.211 failed (Id: 2)

[2017.09.22] 08:23:31 [26127] Initiating connection to 85.158.137.68

[2017.09.22] 08:23:31 [26127] Connecting to 85.158.137.68:25 (Id: 3)

[2017.09.22] 08:23:31 [26127] Binding to local IP 172.27.226.13:0 (Id: 3)

[2017.09.22] 08:23:32 [26127] Exception connecting to 85.158.137.68 (Id: 3)

[2017.09.22] 08:23:32 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 85.158.137.68:25

[2017.09.22] 08:23:32 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 08:23:32 [26127] Connecting to 85.158.137.68:25 (Id: 4)

[2017.09.22] 08:23:53 [26127] Exception connecting to 85.158.137.68 (Id: 4)

[2017.09.22] 08:23:53 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.137.68:25

[2017.09.22] 08:23:53 [26127] Connection to 85.158.137.68 failed (Id: 4)

[2017.09.22] 08:23:53 [26127] Initiating connection to 193.109.254.147

[2017.09.22] 08:23:53 [26127] Connecting to 193.109.254.147:25 (Id: 5)

[2017.09.22] 08:23:53 [26127] Binding to local IP 172.27.226.13:0 (Id: 5)

[2017.09.22] 08:23:54 [26127] Exception connecting to 193.109.254.147 (Id: 5)

[2017.09.22] 08:23:54 [26127] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 193.109.254.147:25

[2017.09.22] 08:23:54 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 08:23:54 [26127] Connecting to 193.109.254.147:25 (Id: 6)

[2017.09.22] 08:24:15 [26127] Exception connecting to 193.109.254.147 (Id: 6)

[2017.09.22] 08:24:15 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 193.109.254.147:25

[2017.09.22] 08:24:15 [26127] Connection to 193.109.254.147 failed (Id: 6)

[2017.09.22] 08:24:15 [26127] Initiating connection to 85.158.143.35

[2017.09.22] 08:24:15 [26127] Connecting to 85.158.143.35:25 (Id: 7)

[2017.09.22] 08:24:15 [26127] Binding to local IP 172.27.226.13:0 (Id: 7)

[2017.09.22] 08:24:36 [26127] Exception connecting to 85.158.143.35 (Id: 7)

[2017.09.22] 08:24:36 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 08:24:36 [26127] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.

[2017.09.22] 08:24:36 [26127] Connecting to 85.158.143.35:25 (Id: 8)

[2017.09.22] 08:24:57 [26127] Exception connecting to 85.158.143.35 (Id: 8)

[2017.09.22] 08:24:57 [26127] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.158.143.35:25

[2017.09.22] 08:24:57 [26127] Connection to 85.158.143.35 failed (Id: 8)

[2017.09.22] 08:24:57 [26127] Initiating connection to 216.82.251.230

[2017.09.22] 08:24:57 [26127] Connecting to 216.82.251.230:25 (Id: 9)

[2017.09.22] 08:24:57 [26127] Binding to local IP 172.27.226.13:0 (Id: 9)

[2017.09.22] 08:24:57 [26127] Connection to 216.82.251.230:25 from 172.27.226.13:51669 succeeded (Id: 9)

[2017.09.22] 08:24:58 [26127] RSP: 220 *****************************************

[2017.09.22] 08:24:58 [26127] CMD: EHLO mail3.claritygo.coma

[2017.09.22] 08:24:58 [26127] RSP: 250-server-11.tower-555.messagelabs.com says EHLO to 46.37.186.167:51669

[2017.09.22] 08:24:58 [26127] RSP: 250-PIPELINING

[2017.09.22] 08:24:58 [26127] RSP: 250-8BITMIME

[2017.09.22] 08:24:58 [26127] RSP: 250 XXXXXXXA

[2017.09.22] 08:24:58 [26127] CMD: MAIL FROM:<bounce-10-1259-6751-6502204-177@clarity-marketing.com>