Hi,

I recently have performed a migration of my company's email server, and now cannot send mail to any of the Messagelabs servers. Are our emails being blocked via a blacklist? I've checked against most of the blacklists I can find and our IP doesn't seem to be on any.

IP in question: 192.99.16.161

Sample error messages: 

Delivery Logs:

13:15:00 [65254] Connection to 216.82.251.36 failed (Id: 22)
13:15:00 [65254] Initiating connection to 85.158.139.103
13:15:00 [65254] Connecting to 85.158.139.103:25 (Id: 23)
13:15:00 [65254] Binding to local IP 192.99.16.161:0 (Id: 23)
13:15:00 [65254] Connection to 85.158.139.103:25 from 192.99.16.161:57944 succeeded (Id: 23)
13:15:00 [65254] RSP: 220 server-12.tower-558.messagelabs.com ESMTP
13:15:00 [65254] CMD: EHLO mail.nllive.ca
13:15:00 [65254] RSP: 250-server-12.tower-558.messagelabs.com says EHLO to 192.99.16.161:57944
13:15:00 [65254] RSP: 250-STARTTLS
13:15:00 [65254] RSP: 250-PIPELINING
13:15:00 [65254] RSP: 250 8BITMIME
13:15:00 [65254] CMD: STARTTLS
13:15:00 [65254] RSP: 220 2.0.0 continue
13:15:00 [65254] CMD: EHLO mail.nllive.ca
13:15:01 [65254] RSP: 250-server-12.tower-558.messagelabs.com says EHLO to 192.99.16.161:57944
13:15:01 [65254] RSP: 250-PIPELINING
13:15:01 [65254] RSP: 250 8BITMIME
13:15:01 [65254] CMD: MAIL FROM:<jay@sandsauto.ca>
13:15:01 [65254] RSP: 250 2.0.0 MAIL FROM accepted
13:15:01 [65254] CMD: RCPT TO:<tdaf_documents@td.com>
13:15:01 [65254] RSP: 421 Service Temporarily Unavailable
13:15:01 [65254] CMD: QUIT

Any help would be appreciated.

Thanks,

Matthew Kean

Systems Administrator

Marquee Inc.

Hi,

Trying to send an email to a client came back the error:

(host cluster6.us.messagelabs.com[216.82.242.46] refused to talk to me: 501 Connection rejected by policy [7.7] 9606, please visit www.messagelabs.com/support for more details about this error message.)

Is it possible to remove our IP from the block list?

IP: 192.95.47.176

Hello,

we currently have the problem that our customer can't send E-Mail to one of their suppliers. Our new mailserver that we recently moved to was on a symantec blacklist and we managed to get it removed from there (http://ipremoval.sms.symantec.com/lookup/) but the suppliers mailserver keeps sending the error: 501 Connection rejected by policy [7.7]

Can you help me to get our mailservers IP [85.214.68.151] removed from all blacklists? 

Thank you,
ggt-soft

Hello,

We are currently having an issue with 2 new VPS. All our clients who are sending to emails to some of their recipients are receiving the following message:

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

The IPs are: 93.190.137.192 and 93.190.137.218

We have just ordered these servers and started using these IPs. It looks like these IPs have been blacklisted previously by the old owner. We have checked with http://ipremoval.sms.symantec.com/lookup/ and the tools says: "does not have a negative reputation and therefore cannot be submitted for investigation. " but our clients keep receiving the 501 error.

Can someone please investigate to whitelist these two IPs.

Thanks.

Vince.

I'm getting the above message from messagelabs.com.  I have completed a blacklist check with MXToolBox and a reputation check on Cisco Talos.

IP Address in question 50.73.29.85

log file entry:

Mon 2017-09-04 16:30:51.135: 01: Parsing message <e:\mdaemon\queues\remote\retry\pd90000000213.msg>
Mon 2017-09-04 16:30:51.135: 01: *  From: sziegler@haverfield.com
Mon 2017-09-04 16:30:51.135: 01: *  To: scott.cantor@pnc.com
Mon 2017-09-04 16:30:51.135: 01: *  Subject: RE: 2016 Financiaks
Mon 2017-09-04 16:30:51.135: 01: *  Size (bytes): 577461
Mon 2017-09-04 16:30:51.135: 01: *  Message-ID: <65fa57ce.1d325ac.11329910.43eb@haverfield.com>
Mon 2017-09-04 16:30:51.135: 05: Resolving MX record for pnc.com (DNS Server: 192.168.1.10)...
Mon 2017-09-04 16:30:51.306: 05: *  P=010 S=000 D=pnc.com TTL=(6) MX=[cluster5.us.messagelabs.com]
Mon 2017-09-04 16:30:51.306: 05: *  P=020 S=001 D=pnc.com TTL=(6) MX=[cluster5a.us.messagelabs.com]
Mon 2017-09-04 16:30:51.306: 05: Attempting SMTP connection to cluster5.us.messagelabs.com
Mon 2017-09-04 16:30:51.306: 05: Resolving A record for cluster5.us.messagelabs.com (DNS Server: 192.168.1.10)...
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.242.34]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.241.195]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.250.83]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.242.147]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.250.99]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.251.35]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.251.36]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.251.37]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.250.51]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.242.131]
Mon 2017-09-04 16:30:51.306: 05: *  D=cluster5.us.messagelabs.com TTL=(14) A=[216.82.242.37]
Mon 2017-09-04 16:30:51.306: 05: Randomly picked 216.82.250.51 from list of possible hosts
Mon 2017-09-04 16:30:51.306: 05: Attempting SMTP connection to 216.82.250.51:25
Mon 2017-09-04 16:30:51.306: 05: Waiting for socket connection...
Mon 2017-09-04 16:31:12.244: 04: *  Socket error 10060 - The connection timed out.
Mon 2017-09-04 16:31:12.244: 05: *  216.82.250.51 added to connection failure cache for 5 minutes
Mon 2017-09-04 16:31:12.244: 05: Attempting SMTP connection to cluster5a.us.messagelabs.com
Mon 2017-09-04 16:31:12.244: 05: Resolving A record for cluster5a.us.messagelabs.com (DNS Server: 192.168.1.10)...
Mon 2017-09-04 16:31:12.244: 05: *  D=cluster5a.us.messagelabs.com TTL=(14) A=[216.82.251.230]
Mon 2017-09-04 16:31:12.244: 05: *  D=cluster5a.us.messagelabs.com TTL=(14) A=[85.158.139.103]
Mon 2017-09-04 16:31:12.244: 05: Randomly picked 85.158.139.103 from list of possible hosts
Mon 2017-09-04 16:31:12.244: 05: Attempting SMTP connection to 85.158.139.103:25
Mon 2017-09-04 16:31:12.244: 05: Waiting for socket connection...
Mon 2017-09-04 16:31:12.354: 05: *  Connection established 192.168.1.16:4239 --> 85.158.139.103:25
Mon 2017-09-04 16:31:12.354: 05: Waiting for protocol to start...
Mon 2017-09-04 16:31:12.463: 02: <-- 220 server-14.tower-558.messagelabs.com ESMTP
Mon 2017-09-04 16:31:12.463: 03: --> EHLO haverfield.com
Mon 2017-09-04 16:31:12.573: 02: <-- 250-server-14.tower-558.messagelabs.com says EHLO to 50.73.29.85:4239
Mon 2017-09-04 16:31:12.573: 02: <-- 250-STARTTLS
Mon 2017-09-04 16:31:12.573: 02: <-- 250-8BITMIME
Mon 2017-09-04 16:31:12.573: 02: <-- 250 PIPELINING
Mon 2017-09-04 16:31:12.573: 03: --> STARTTLS
Mon 2017-09-04 16:31:12.682: 02: <-- 220 2.0.0 continue
Mon 2017-09-04 16:31:13.135: 05: SSL negotiation successful (TLS 1.0, 2048 bit key exchange, 128 bit RC4 encryption)
Mon 2017-09-04 16:31:13.135: 03: --> EHLO haverfield.com
Mon 2017-09-04 16:31:13.244: 02: <-- 250-server-14.tower-558.messagelabs.com says EHLO to 50.73.29.85:4239
Mon 2017-09-04 16:31:13.244: 02: <-- 250-8BITMIME
Mon 2017-09-04 16:31:13.244: 02: <-- 250 PIPELINING
Mon 2017-09-04 16:31:13.244: 03: --> MAIL From:<prvs=14201c4baf=sziegler@haverfield.com>
Mon 2017-09-04 16:31:13.354: 02: <-- 250 2.0.0 MAIL FROM accepted
Mon 2017-09-04 16:31:13.354: 03: --> RCPT To:<scott.cantor@pnc.com>
Mon 2017-09-04 16:31:13.463: 02: <-- 421 Service Temporarily Unavailable
Mon 2017-09-04 16:31:13.463: 03: --> QUIT
Mon 2017-09-04 16:31:13.463: 01: *  This message is 0 days old; it has 2 days left to get delivered
Mon 2017-09-04 16:31:13.463: 04: SMTP session terminated (Bytes in/out: 350/227)
Mon 2017-09-04 16:31:13.463: 01: ----------

Any Help would be greatly appreciated.

Thanks

I'm getting the above message from server-13.tower-558.messagelabs.com.  I have completed a blacklist check with MXToolBox and a reputation check on Cisco Talos.

IP address in question: 50.73.29.85

Any Help would be greatly appreciated.

Thanks

Hello,

We are currently unable to send to many domains that use the Symantec Cloud for spam filtering Up to about 48 hours ago, we had no issues in sending emails these emails. We have a very large 
number of receipents that have been affected. Please see error response below.

I have looked at the read me supply by the link below, but there's nothing there that indicates what might be causing not been able to send emails to these receipents. Our SPF/DKIM records are setup correctly. 
Our sending IP address is not blacklisted.

The content of the email has not changed. I would be grateful if maybe I could be able to find out the issue and hopefully resolve as quickly as possible.

I can supply any further information that might be required.

Thank you in Advance for any help that can be supplied.

Best Regards

Darren

Your message did not reach some or all of the intended recipients:
<removed>

Error Type: SMTP
   Remote server (85.158.137.83) issued an error.
   hMailServer sent: .
   Remote server replied: 553-Message filtered. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)

Hi,

We have domain in G-Suite for mail purpose. we are sending mail to few client and get's bounce back to us.

Its Saying Symantec mail filter error. We suspect our domain get's blocklisted by symantec but still we are not doing any spaming activity.

We couldn't get ipaddress because its in Google cloud.

So could you please advise how to send delist request by Domain Address.

-Thanks

Vignesh

Hello -

I have a customer who I'm told formerly used Symantec's email security product, but has migrated to and uses Office365 - thus the Symantec product was dropped for them.

However, they have a business partner who does use Symantec Email Security. Their email system reports the email was successfully delivered, Symantec is reporting it delivered, but it is never making it to the Office365 service. The mail logs at Office365 do not see any attempt of delivery, rejection, etc of the mail from the remote domain. Microsoft confirms these findings.

I believe that the Symantec system is delivering the mail to the setup it sees for the customer in the Symantec system and is never actually delivering the email to the MX record.

I do not see any support option for this and the business partner has maintained that the issue is not on their end as it shows delivered.

What would my options be with getting this resolved (or at least ruled out) at Symantec?

Our mail server IP 65.157.63.242 is unable to connect to messagelabs, for example IP 216.82.241.243. We are not on any blacklists. Can you please remove throttling for our IP?

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?

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.

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!

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.

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

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)

I would appreciate if anyone could help to this matter.

Thank you very much and good day.

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.

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

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

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 ?