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

$

0

0

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.

0

---

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

$

0

0

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.

0

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

$

0

0

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.

0

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

$

0

0

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

0

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

$

0

0

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...

0

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

$

0

0

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.

0

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

$

0

0

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.

0

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

$

0

0

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.

0

• 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

$

0

0

I need a solution

0

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?

$

0

0

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>

[2017.09.22] 08:24:58 [26127] RSP: 250 2.0.0 MAIL FROM accepted

[2017.09.22] 08:24:58 [26127] CMD: RCPT TO:<jessica.barrett@principleglobal.com>

[2017.09.22] 08:24:59 [26127] RSP: 421 Service Temporarily Unavailable

[2017.09.22] 08:24:59 [26127] CMD: QUIT

[2017.09.22] 08:25:04 [26127] Bounce email written to 141402126503.eml

[2017.09.22] 08:25:04 [26127] Delivery for bounce-10-1259-6751-6502204-177@clarity-marketing.com to jessica.barrett@principleglobal.com has completed (Bounced)

[2017.09.22] 08:25:05 [26127] Delivery finished for bounce-10-1259-6751-6502204-177@clarity-marketing.com at 08:25:05[id:141402126127]

0

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

September 27, 2017, 8:53 pm

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

≪ Previous: 421 response despite mail being delivered

$

0

0

I need a solution

Hi

Our organisation has implemented Mimecast for our email security.  We have some users who are using a application and uses it to send out emails to other users of the same application.

However, we get emails bounced back, due to Mimecast detecting a different IP address everytime the email gets sent out via Messagelabs and sees it as spoofing when it is not.

Can anyone provide the IP Source Range for Messagelabs:

mail1.bemta5.messagelabs.com's source IP range

Thanks!

0

501 Connection rejected by policy [7.7] 20105

September 28, 2017, 8:27 am

≫ Next: Error returned when emailing Messagelabs clients

≪ Previous: Require Messagelabs IP source IP range (mail1.bemta5.messagelabs.com)

$

0

0

I need a solution

 

We have some problem send email to astrid.febrina@se1.bp.com and another email under cluster messagelabs.com

 

The following error report : 

 

 

Reporting-MTA: dns; mx651.qwords.net

Action: failed
Final-Recipient: rfc822;astrid.febrina@se1.bp.com
Status: 5.0.0
Remote-MTA: dns; cluster8.us.messagelabs.com
Diagnostic-Code: smtp; 501 Connection rejected by policy [7.7] 20105, please visitwww.messagelabs.com/support for more details about this error message.

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:

  astrid.febrina@se1.bp.com
    host cluster8.us.messagelabs.com [216.82.242.45]
    SMTP error from remote mail server after initial connection:
    501 Connection rejected by policy [7.7] 20105, please visitwww.messagelabs.com/support for more details about this error message.

We are using Spamfilter for outgoing email and not open relay, The list of our ip cluster : 

 

103.195.91.242

103.28.12.51

43.252.136.242

43.252.136.14

209.58.179.211

209.58.179.212

209.58.179.213

 

We try to check our reputation IP in :

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

 

Our IP Does not have negative reputation, 

 

Please help to resolve the problem

 

Regards,

Arifin C

0

Error returned when emailing Messagelabs clients

October 2, 2017, 1:43 pm

≫ Next: rejected email - The following organization rejected your message: server-3.tower-184.messagelabs.com.

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

$

0

0

I need a solution

Hi,

[I posted in a topic but I think it may be best to post as a new topic]

My client has encountered this error sending an email to a contact:

Remote Server returned '554 5.0.0 <removeddomainforprivacy.com #5.0.0 smtp;message text rejected by cluster9.us.messagelabs.com: 553 information. (#5.7.1)>'

x-originating-ip: [96.69.125.106]

I believe this is the same issue as on the beginning of this thread.

Earlier this week I was brought on to clean a malware infection and remove blacklisting on their domain. This may be a leftover from this?

edit: as have others I checked http://ipremoval.sms.symantec.com/lookup/ but it does not recognize the ip.

Can you help clarify?

Many thanks

0

rejected email - The following organization rejected your message: server-3.tower-184.messagelabs.com.

October 3, 2017, 2:43 pm

≫ Next: cluster3.eu.messagelabs.com refused to talk to me: 501 Connection rejected by policy [7.7] 9002

≪ Previous: Error returned when emailing Messagelabs clients

$

0

0

I need a solution

Hi my administrators have told me they cannot resolve an issue with my emails to a specific inbox we use. I can receive from it but cannnot send to it which is very important for us. below is the error I am getting:

The following organization rejected your message: server-3.tower-184.messagelabs.com.

Any help would be greatly appreciated.

Thanks,

Michael

0

cluster3.eu.messagelabs.com refused to talk to me: 501 Connection rejected by policy [7.7] 9002

October 4, 2017, 7:08 am

≫ Next: 350 Remote server returned an error -> 553 you are trying to use me [server-2.tower-206.messagelabs;.com] as a relay, but I have not been configured to let;you [40.107.5.74, mail-eopbgr50074.outbound.protection.o;utlook.com] do this.

≪ Previous: rejected email - The following organization rejected your message: server-3.tower-184.messagelabs.com.

$

0

0

I need a solution

Hi,

When my domain (fontaineinsertion.fr) tries to write mails to the different recipient of domains (…@schneider-electric.com) and (...@sdf.fr). We have the error messages:

: host
cluster3.eu.messagelabs.com[85.158.139.3] refused to talk to me: 501
Connection rejected by policy [7.7] 9002, please visit
www.messagelabs.com/support for more details about this error message.

Or

: host cluster1.eu.messagelabs.com[85.158.136.227] refused to
talk to me: 501 Connection rejected by policy [7.7] 16209, please visit
www.messagelabs.com/support for more details about this error message.

Can you investigate my problem?

My Server ip 213.246.62.66
I already check http://ipremoval.sms.symantec.com/lookup/, but my IPs does not have a negative reputation

I followed your procedure twice a few weeks ago. (https://support.symantec.com/en_US/article.TECH828...) I still have no replies

If you need more information, contact to me.

Best regards,

ROTH Charlie

0

---

350 Remote server returned an error -> 553 you are trying to use me [server-2.tower-206.messagelabs;.com] as a relay, but I have not been configured to let;you [40.107.5.74, mail-eopbgr50074.outbound.protection.o;utlook.com] do this.

October 4, 2017, 4:40 am

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

≪ Previous: cluster3.eu.messagelabs.com refused to talk to me: 501 Connection rejected by policy [7.7] 9002

$

0

0

I need a solution

Hi,

When Office 365 tried to send your message, the receiving email server outside Office 365 reported an error.

The domain is soderkyl.se

I will provide the bounceback below:

Original Message Details

Created Date: 10/4/2017 7:24:39 AM Sender Address: oscar.lundborg@systemetit.se Recipient Address: Anders.Kols@soderkyl.se Subject: SV: Test1

Error Details

Reported error: 550 5.0.350 Remote server returned an error -> 553 you are trying to use me [server-2.tower-206.messagelabs;.com] as a relay, but I have not been configured to let;you [40.107.5.74, mail-eopbgr50074.outbound.protection.o;utlook.com] do this. Please visit;www.symanteccloud.com/troubleshooting for more details;about this error message and instructions to resolve;this issue. (#5.7.1) DSN generated by: AM6PR0402MB3621.eurprd04.prod.outlook.com Remote server: server-2.tower-206.messagelabs.com

Message Hops
HOP	TIME (UTC)	FROM	TO	WITH	RELAY TIME
1	10/4/2017 7:24:39 AM	AM6PR0402MB3623.eurprd04.prod.outlook.com	AM6PR0402MB3623.eurprd04.prod.outlook.com	mapi	*
2	10/4/2017 7:24:39 AM	AM6PR0402MB3623.eurprd04.prod.outlook.com	AM6PR0402MB3621.eurprd04.prod.outlook.com	Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)	*

Original Message Headers

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

 d=roslagsgatannu.onmicrosoft.com; s=selector1-systemetit-se;

 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;

 bh=GkR17ugZEGpECNsIBqY/PxkbG4L/lPz9qnnlPUbifRI=;

 b=oddIqnRp+/Ns0rtSFBZtODPjIPXA4+zDSvT/Hta0S1dMYR8h6KuM3P/eZD6Dui66XQcf3O9CxlYL4YHiTHjHKMFgl2wCXCWT4V5iyNz4zkcrWnJ+CVZ+EsRZO4c9jmwQcRJpjPIB+fcMGRfzibtKpG4r2kbD72yiPzoG55uxbEI=

Received: from AM6PR0402MB3623.eurprd04.prod.outlook.com (52.133.20.24) by

 AM6PR0402MB3621.eurprd04.prod.outlook.com (52.133.20.22) with Microsoft SMTP

 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id

 15.20.77.7; Wed, 4 Oct 2017 07:24:39 +0000

Received: from AM6PR0402MB3623.eurprd04.prod.outlook.com

 ([fe80::4921:dabe:56b8:ecf5]) by AM6PR0402MB3623.eurprd04.prod.outlook.com

 ([fe80::4921:dabe:56b8:ecf5%13]) with mapi id 15.20.0077.018; Wed, 4 Oct 2017

 07:24:39 +0000

From: Oscar Lundborg <oscar.lundborg@systemetit.se>

To: Anders Kols <Anders.Kols@soderkyl.se>

Subject: SV: Test1

Thread-Topic: Test1

Thread-Index: AdM84gadd0cFoQkJQdijgSfTQ6CvsAAADPAg

Date: Wed, 4 Oct 2017 07:24:39 +0000

Message-ID: <AM6PR0402MB3623C193B36361DBB560348C82730@AM6PR0402MB3623.eurprd04.prod.outlook.com>

References: <HE1PR0501MB28609CE7096FF1ED9EDD8A4BE9730@HE1PR0501MB2860.eurprd05.prod.outlook.com>

In-Reply-To: <HE1PR0501MB28609CE7096FF1ED9EDD8A4BE9730@HE1PR0501MB2860.eurprd05.prod.outlook.com>

Accept-Language: en-US, sv-SE

Content-Language: sv-SE

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

authentication-results: spf=none (sender IP is )

smtp.mailfrom=oscar.lundborg@systemetit.se; 

x-originating-ip: [213.132.98.158]

x-ms-publictraffictype: Email

x-microsoft-exchange-diagnostics: 1;AM6PR0402MB3621;6:cz5NARU1mFs4AHqhJlw7LfFGmJB8mDTFP0hu/1zm1t0jR0jxGmLRb6yKUL5P95+xVDz5gGj1Rlhlz99GObjQ9Wl+R9EVUNxReJE9uoSeaxMzFhVOlhA446AJxbInOBbKNhbJzJnfO6rCeLo6yR/xYG4XwuPTXgP58LhEWOiNyivVpAndQewlXpKttRbJfWtqxeps+ox5/lO1f4oA2TYotBU3GSFxvcmyQe8f8pS+a/SAtgy2MQiDNanpiiJo9eQ9pefmZXSdG+8Ur8j0t0GeEfQI0ob3zG70G8ylS3dv6AdEyxVZJJl4oQ2SSTSUBMv/Y07VvYa7EdEJwsh3vcTfWQ==;5:EtDLHMYw2vngI5oDmB+7NKjO/zYX1Seuys+Ctp+12f0eoN4+FtpJr8LS/8nKGfnoYGqe17dZmj2FdH5+aPukeESipsLfgSMB7QHsNWXpZPhUiypuOjMnuv0Yut6u0vDmxFMwZtba7xUgsENJhlSgGw==;24:NayFIHhX5aILgVdso3sg+dyf9+lEk4XQSu5rcYaV0jbLq+T2rcq8AC1nPAUUy+vEFq3/0LyhmcaSPgIIc9usWnK8vpALr/4L58IKmi7bvVo=;7:Kl22YUBc5KZL0bqqGP8W86iHkwLiVU0navGZUI3p4uI0rM1GgmrY9zA9+ilWpoyVeuRODZ1dlW02UrQWYfLqDrSQ5ppZ1EJkDqOHPbSrhbczdGZYRvAaZ7j4G6pCobkUu5HpxG160DRcsKNrjY8Q5gak8WgSLv8GrZjewFAJVlX2wLMJ62Uv7xzYzPYkNZO5z+MdEWvLKKkNR76B+DAcMR188izC/GLmtemr67aRrgQ=

x-ms-exchange-antispam-srfa-diagnostics: SSOS;

x-ms-office365-filtering-correlation-id: bd77f3f8-b7fe-4b83-f840-08d50af8f93b

x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254152)(2017082002075)(2017052603199)(49563074)(201703131423075)(201702281549075);SRVR:AM6PR0402MB3621;

x-ms-traffictypediagnostic: AM6PR0402MB3621:

x-exchange-antispam-report-test: UriScan:(21748063052155);

x-microsoft-antispam-prvs: <AM6PR0402MB36213AFD2F673C8470C9D80982730@AM6PR0402MB3621.eurprd04.prod.outlook.com>

x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(2401047)(5005006)(8121501046)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(6041248)(20161123562025)(2016111802025)(20161123555025)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(6043046)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095);SRVR:AM6PR0402MB3621;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:AM6PR0402MB3621;

x-forefront-prvs: 0450A714CB

x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(346002)(39830400002)(376002)(199003)(189002)(6306002)(7696004)(54896002)(33656002)(236005)(14454004)(2900100001)(68736007)(6916009)(66066001)(74482002)(733005)(6436002)(7116003)(101416001)(9686003)(2950100002)(86362001)(5660300001)(6506006)(606006)(55016002)(99286003)(478600001)(105586002)(53376002)(54556002)(97736004)(106356001)(53386004)(99936001)(3846002)(102836003)(25786009)(5250100002)(53936002)(8676002)(316002)(76176999)(6116002)(50986999)(3660700001)(81156014)(81166006)(8936002)(74316002)(790700001)(3280700002)(189998001)(7736002)(54356999)(2906002)(16866105001)(15398625002);DIR:OUT;SFP:1101;SCL:1;SRVR:AM6PR0402MB3621;H:AM6PR0402MB3623.eurprd04.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:sv;

received-spf: None (protection.outlook.com: systemetit.se does not designate

 permitted sender hosts)

spamdiagnosticoutput: 1:99

spamdiagnosticmetadata: NSPM

Content-Type: multipart/related;

        boundary="_006_AM6PR0402MB3623C193B36361DBB560348C82730AM6PR0402MB3623_";

        type="multipart/alternative"

MIME-Version: 1.0

X-OriginatorOrg: systemetit.se

X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2017 07:24:39.0386

 (UTC)

X-MS-Exchange-CrossTenant-fromentityheader: Hosted

X-MS-Exchange-CrossTenant-id: 25a43fa0-f5da-4140-a2fb-94c74f685876

X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR0402MB3621

Could you please assist us in this case since its really urgent.

The customer cannot receive any emails from outside the organization.

It's about 200+ emails waiting on inbound. 

0

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

October 4, 2017, 6:19 am

≫ Next: How I can send an email encrypted to hotmail or gmail?

≪ Previous: 350 Remote server returned an error -> 553 you are trying to use me [server-2.tower-206.messagelabs;.com] as a relay, but I have not been configured to let;you [40.107.5.74, mail-eopbgr50074.outbound.protection.o;utlook.com] do this.

$

0

0

I need a solution

Good morning,

We have incountered a spike in Symantec bounces over the last few days. We are sending Pharmaceutical marketing and educational content on behalf of several Pharma companies to targeted lists of doctors and  physicians exclusively. It is vital that this information is sent and received.

Symantec cloud has blocked the mail to several hundred email receivers.

I have followed instructions to the letter in your false positive submission article. Interestingly the team does not respond at all to these submissions.

Our IPs are not blocked by Symantec or any third party service. Here are a list of our IPs

167.89.127.10
168.245.17.146
 

Please accept this request to review our pharma content as it is getting caught in your filter.

0

• Test - Dont Leave HER2 Exposed.txt

How I can send an email encrypted to hotmail or gmail?

October 5, 2017, 8:44 am

≫ Next: New ISTR Special Report: Email Threats 2017

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

$

0

0

I need a solution

Hi all,

This is a question about the function of email cloud. The configuration of TLS is clear and I configured this step and I understand that the domains that are in the partners list talk secured. My question is (really the question comes from the customer) how I can send an email to another user that has an account in gmail (or hotmail, yahoo, etc.). Are there a special configuration to do this?

Regards,

Carlos Espinoza

0

New ISTR Special Report: Email Threats 2017

October 5, 2017, 9:17 am

≫ Next: MessageLabs

≪ Previous: How I can send an email encrypted to hotmail or gmail?

$

0

0

I do not need a solution (just sharing information)

Just raising awareness of a new (free!) white paper from Symantec Security Response!

The latest ISTR special report, Email Threats 2017, casts a light on a threat landscape where attackers are actively spreading malicious threats, BEC scams, and a variety of spam through email.

Full white paper: https://www.symantec.com/content/dam/symantec/docs/security-center/white-papers/istr-email-threats-2017-en.pdf

0

MessageLabs

October 8, 2017, 7:05 pm

≫ Next: Sending mails to schneider-electric.com

≪ Previous: New ISTR Special Report: Email Threats 2017

$

0

0

I do not need a solution (just sharing information)

I'm having trouble corresponding with a few of my clients who have servers behind MessageLabs infrastructure. 

There seems to be an error in delivery. I'm corresponding from ncinl.ca (IP is 67.202.92.9) and cansel.ca.

IP:

67.202.92.9

DNS: 

ns22.wpxhosting.com
ns23.wpxhosting.com

I've double checked the following:

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

Email still don't reach any recepient within the target domain.

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

Regards

Daniel

0