Server Blacklist removal

January 4, 2018, 2:20 pm

≫ Next: IP Blacklist removal

≪ Previous: Server Blacklist Removal

$

0

0

I need a solution

Hi, 

One our clients is having trouble sending / receiving emails, and we believe this is due to a IP blacklist issue, as our clients IP address was recently changed. 

Could you remove the blacklist on the IP 148.59.198.211 please and thank you. 

Below are examples of the errors they receive when sending / receiving from one of your mail clients. 

Any help with this issue would be greatly appreciated, 

Thanks.

-----------------------------------------------------------------

Message ID : 

Sent Date : Wed, 20 Dec 2017 10:51:28 -0700

From : postmaster@weldco-beales.com

Sender MailID : postmaster@weldco-beales.com

Reply To : postmaster@weldco-beales.com

To : jlindsay@weldco-beales.com

Subject : Undeliverable: FW: Invoice 4SI14998



------------------------- Contents -------------------------



Your message



To: tspruce@orgaworld.ca

Cc: Tami Dyer

Subject: FW: Invoice 4SI14998

Sent: Mon, 18 Dec 2017 08:39:19 -0700



did not reach the following recipient(s):



tspruce@orgaworld.ca on Wed, 20 Dec 2017 10:51:27 -0700

Could not deliver the message in the time limit specified. Please

retry or contact your administrator.

 

---------------------------------------------------------------------

From: System Administrator
Sent: Sunday, December 17, 2017 11:54 AM
To: Jamie Lindsay
Subject: Undeliverable: FW: Invoice 4SI14998

Your message did not reach some or all of the intended recipients.

      Subject:  FW: Invoice 4SI14998

      Sent:     12/15/2017 8:13 AM

The following recipient(s) cannot be reached:

      tspruce@orgaworld.ca on 12/17/2017 11:53 AM

            Could not deliver the message in the time limit specified.  Please retry or contact your administrator.

            <WBM2-EXCHGFI01.weldco-beales.local #4.4.7>

-------------------------------------------------------------

0

---

IP Blacklist removal

January 5, 2018, 4:38 am

≫ Next: Mail delay from messagelabs.com

≪ Previous: Server Blacklist removal

$

0

0

I need a solution

This problem has been going on for months, and my users are getting very frustrated. 

Any mail that we send out that goes through messagelabs.com isn;'t delivered because messagelabs won't communicate on port 25 with my 207.34.224.106 address.   If I connect on an alternate ip they answer so it's not a routing issue, but an ip blocking issue.  See logs below.

I went to the page to check my ip's reputation and it says "The IP address you submitted, 207.34.224.106, does not have a negative reputation and therefore cannot be submitted for investigation." but they are obviously blocking us.

Can someone please look into this?  Thank You

========================

= Session Transcript =

========================

 

Session 820733; child 0001

Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd35001039933.msg>

* From: glen.uttley@melloul.com

* To: Vaughan.MacDonald@td.com

* Subject: RE: [Confidential] test

* Size (bytes): 13054

* Message-ID: <002301d3858a$8fe66b20$afb34160$@melloul.com>

Resolving MX record for td.com (DNS Server: 8.8.8.8)...

* P=010 S=000 D=td.com TTL=(59) MX=[cluster5.us.messagelabs.com]

* P=020 S=001 D=td.com TTL=(59) MX=[cluster5a.us.messagelabs.com]

Attempting SMTP connection to cluster5.us.messagelabs.com

Resolving A record for cluster5.us.messagelabs.com (DNS Server: 8.8.8.8)...

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.250.51]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.241.195]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.251.36]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.251.35]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.242.34]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.250.83]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.250.99]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.242.37]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.242.131]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.242.147]

* D=cluster5.us.messagelabs.com TTL=(11) A=[216.82.251.37]

Randomly picked 216.82.242.131 from list of possible hosts

Attempting SMTP connection to 216.82.242.131:25

Waiting for socket connection...

* Socket error 10060 - The connection timed out.

* 216.82.242.131 added to connection failure cache for 5 minutes

Attempting SMTP connection to cluster5a.us.messagelabs.com

Resolving A record for cluster5a.us.messagelabs.com (DNS Server: 8.8.8.8)...

* D=cluster5a.us.messagelabs.com TTL=(3) A=[216.82.251.230]

Attempting SMTP connection to 216.82.251.230:25

Waiting for socket connection...

* Socket error 10061 - The other host is either down or has refused to connect with you at that IP and/or on that port.

* This message is 63 minutes old; it has 0 minutes left in this queue

Remote queue lifetime exceeded; message placed in retry queue

 

========================

= End Transcript =

========================

0

Mail delay from messagelabs.com

January 9, 2018, 2:16 am

≫ Next: 100% smtp;553 Message filtered - Newsletter to paid subscriptions only - False Positive email attached for analysis

≪ Previous: IP Blacklist removal

$

0

0

I need a solution

Hello,

We had many problem to received mail from your gateway *.messagelabs.com.

The mail arrived corretly but with many delay (sometime 2-3 hours or 2 days).
It's not possible to talk with our clients with this delay.

We had few example with many clients.

I had already created a ticket on the mail investigation@review.symantec.com but he does not response since 7 days.

For example, i can send you few headers (in private)

Thanks for your help

0

• Delay_messagelabs.png

100% smtp;553 Message filtered - Newsletter to paid subscriptions only - False Positive email attached for analysis

January 10, 2018, 5:01 am

≫ Next: Emails getting rejected

≪ Previous: Mail delay from messagelabs.com

$

0

0

I need a solution

Hi Symantec,

Subscribers are calling upset they are not receiving the subscription emails they have paid for. 

About 8 days ago our client started to get 553 bounceback errors to contacts we've been sending to all along. This daily Newsletter goes only to subscribers that have paid an annual fee and there have not been any changes to template of sign-up method compared to previous months. DKIM and SPF records all check out cleanIP hasn't been in any blacklist. I've submitted the domain information, delivery log overview, when the bounce started and false positive example yesterday 09 Jan 11:39 to noreply@connect.symantec.com, but haven't received a reply and no change in sending ability.

What other options do we have to get this resolved by Symantec?

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

t dsnMta                              cluster3.eu.messagelabs.com (redacted)

X-SpamInfo: spam detected heuristically

0

Emails getting rejected

January 10, 2018, 12:51 pm

≫ Next: Mails not arriving to MessageLabs/Symantec clients

≪ Previous: 100% smtp;553 Message filtered - Newsletter to paid subscriptions only - False Positive email attached for analysis

$

0

0

I need a solution

Hello there,

         One of our clients emails are being rejected during the data command phase of the SMTP transcation. It looks like after the initial RCPT TO command we are receving 250ok but during the data commad transcation message labs is rejecting our message and returning SMTP error  550 b7a91550-d106-11e7-8b96-d3e765ac3bf9 Message delivery rejected  I've verified our sending IP doesn't have a negative reputation

         Could you please let me know how we could resolve this issue? I can send additional information like copy of full bounce message through private message

Thanks,

vsri

0

Mails not arriving to MessageLabs/Symantec clients

January 11, 2018, 4:39 am

≫ Next: My server IP is blocked

≪ Previous: Emails getting rejected

$

0

0

I need a solution

Hello,

Unfortunately we have been experimented a lot of business problem, durint the last couple years, because of your service.

We understand perfectly right that it is a very important contribution to Internet the implementation of security policy to reduce spam and a lot of undesirable e-mails. But the problem is not here. The problem is that it is practically impossivel to found a way to remove our IPs from your blacklisted.

By this reason, we are posting here by the first time with the hope someone of Symantec can contribute to resolve this situation, considering that we are not sending spam or even newsletters to our customers.

We have the followings publics IPs:

69.64.73.138
69.64.73.36
69.64.73.174
69.64.73.169

And we will apreciate a lot that this IPs could be removed from any blacklisted in your server.

Aditionally, our mail server is reporting in queue the following messages:

host cluster4a.eu.messagelabs.com[85.158.139.103] said: 421 Service Temporarily Unavailable (in reply to RCPT TO command)

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

host cluster4a.us.messagelabs.com[216.82.251.230] said: 421 Service Temporarily Unavailable (in reply to RCPT TO command)

delivery temporarily suspended: lost connection with cluster4a.eu.messagelabs.com[85.158.139.103] while sending RCPT TO

I will be attentive to any comment.

Kind Regards,

Felipe Betancourt.

0

My server IP is blocked

January 12, 2018, 3:11 am

≫ Next: Cannot send emails to messagelabs customers

≪ Previous: Mails not arriving to MessageLabs/Symantec clients

$

0

0

I need a solution

Hello,

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

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

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

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

LOG: MAIN

(connect to cluster8.us.messagelabs.com[216.82.241.132]:25: Connection timed out)

0

Cannot send emails to messagelabs customers

January 12, 2018, 5:24 am

≫ Next: Cannot send emails to messagelabs.com

≪ Previous: My server IP is blocked

$

0

0

I need a solution

One of our clients cannot send emails to messagelabs customers.

"553-Message filtered. Refer to the Troubleshooting page at  553-http://www.symanteccloud.com/troubleshooting"

I've used the lookup tool and cannot see anything wrong. I've seen a similar thread in which admins found that the IP was being throttled and were able to refresh the status.

Could you check IPs 91.227.208.0/24

and tell me if this is a similar situation?

Thanks for your time

0

---

Cannot send emails to messagelabs.com

January 12, 2018, 7:15 am

≫ Next: 521 Service Temporarily Unavailable

≪ Previous: Cannot send emails to messagelabs customers

$

0

0

I need a solution

    host cluster1a.us.messagelabs.com [216.82.251.230]
    Delay reason: SMTP error from remote mail server after RCPT TO:<TFischer@aoc-resins.com>:
    421 Service Temporarily Unavailable

Return-path: <nmyszka@roma.torun.pl>
Received: from gfw132.internetdsl.tpnet.pl ([83.12.152.132] helo=[192.168.0.103])
	by t800.octsys.pl with esmtpa (Exim 4.89_1)
	(envelope-from <nmyszka@roma.torun.pl>)
	id 1eZY5d-0005XO-3i
	for TFischer@aoc-resins.com; Thu, 11 Jan 2018 09:19:58 +0100
Subject: =?UTF-8?Q?Re:_Oferta_na_=c5=bcywic=c4=99_Vipel_F-010?=
To: "Fischer, Tomasz"<TFischer@aoc-resins.com>
References: <e2f4583a-da60-4cf8-c1fd-5ed914156e45@roma.torun.pl><6db4470d61e940b29f663b8339150293@AOCCOL-42.aoc-resins.com><2dc7c6b5-5296-4061-5e21-e6b8343f74d9@roma.torun.pl><83706c009a744818b8cb015cb62f0fcb@AOCCOL-42.aoc-resins.com>
From: Natalia Myszka <nmyszka@roma.torun.pl>
Message-ID: <3efa7f36-b3ab-0d5d-85c7-efe156973350@roma.torun.pl>
Disposition-Notification-To: Natalia Myszka <nmyszka@roma.torun.pl>
Date: Thu, 11 Jan 2018 09:19:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <83706c009a744818b8cb015cb62f0fcb@AOCCOL-42.aoc-resins.com>
Content-Type: multipart/alternative;
 boundary="------------B276F480AAA61016B6095B6D"
Content-Language: pl

0

521 Service Temporarily Unavailable

January 14, 2018, 10:56 am

≫ Next: MessageLabs blocking emails error 501

≪ Previous: Cannot send emails to messagelabs.com

$

0

0

I need a solution

Hi,

A client using my server for emails is having issues sending emails to a client using your service. The errors are:

Jan 14 18:03:41 trs1 sendmail[25134]: w09HNgxC021984: to=<xxxxx.xxxxx@MCGA.GOV.UK>, 
delay=5+00:39:59, xdelay=00:00:01, mailer=esmtp, pri=11011575, relay=cluster3a.eu.messagelabs.com. [85.158.139.103], 
dsn=4.0.0, stat=Deferred: 421 Service Temporarily Unavailable

Can you see if our IP has been temporarily blacklisted or why their emails are not getting through please??
The IP server address is 52.50.18.49

Kind Regards
Tony 

0

MessageLabs blocking emails error 501

January 14, 2018, 12:25 pm

≫ Next: Mail server blocked by Messagelabs

≪ Previous: 521 Service Temporarily Unavailable

$

0

0

I need a solution

Hello, we've had this issue for a while and have already exhausted trying to communicate directly with the receiving party.  More often than not, they are clueless as to how to remove us from whatever list is being maintained that is blocking our emails and those who seem to have a bit of technical knowledge always claim that they have no control over it.

I've tried reaching out to my data center directly who has already tried to whitelist through other means without success so I am opening a ticket here (after several months of trying everything else) as a last resource.

Here is the blocked message.  I am using *** to protect some of the email addresses here but happy to provide these privately if need be.  I've also emailed this to the email that is being provided in different similar threads here but have not had a response.

The originating IP that is being blocked is: 107.174.26.221.  This particular IP  I have it exclusively assigned to a single customer so that I am not blocking the entire server.  Here is the email log error:

Hello, this message is intended for your IT department or whoever handles your email service.  We are a Web Hosting company and emails from our servers are being filtered / blocked by yours.  As a consequence, legitimate communication from my clients to your servers are being rejected and thus why I've contacted you today.  I am pasting below the actual error message so you can have your IT department troubleshoot and possibly remove us from such blockage.

Thanks!

The source IP address is: 107.174.26.221

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1ea0NW-00041X-4v
delivering 1ea0NW-00041X-4v
LOG: MAIN
  Sender identification U=countsy5 D=countryclub.do S=***@countryclub.do
Connecting to cluster1.us.messagelabs.com [216.82.241.131]:25 from 107.174.26.221 ... connected
  SMTP<< 501 Connection rejected by policy [7.7] 5405, please visit www.messagelabs.com/support for more details about this error message.
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  H=cluster1.us.messagelabs.com [216.82.241.131]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 5405, please visit www.messagelabs.com/support for more details about this error message.
Connecting to cluster1.us.messagelabs.com [216.82.249.179]:25 from 107.174.26.221 ... connected
  SMTP<< 501 Connection rejected by policy [7.7] 4408, please visit www.messagelabs.com/support for more details about this error message.
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  H=cluster1.us.messagelabs.com [216.82.249.179]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 4408, please visit www.messagelabs.com/support for more details about this error message.
Connecting to cluster1.us.messagelabs.com [216.82.241.243]:25 from 107.174.26.221 ... connected
  SMTP<< 501 Connection rejected by policy [7.7] 19209, please visit www.messagelabs.com/support for more details about this error message.
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  H=cluster1.us.messagelabs.com [216.82.241.243]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 19209, please visit www.messagelabs.com/support for more details about this error message.
Connecting to cluster1.us.messagelabs.com [216.82.249.211]:25 from 107.174.26.221 ... connected
  SMTP<< 501 Connection rejected by policy [7.7] 5307, please visit www.messagelabs.com/support for more details about this error message.
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  H=cluster1.us.messagelabs.com [216.82.249.211]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 5307, please visit www.messagelabs.com/support for more details about this error message.
Connecting to cluster1.us.messagelabs.com [216.82.242.44]:25 from 107.174.26.221 ... connected
  SMTP<< 501 Connection rejected by policy [7.7] 19704, please visit www.messagelabs.com/support for more details about this error message.
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  H=cluster1.us.messagelabs.com [216.82.242.44]: SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 19704, please visit www.messagelabs.com/support for more details about this error message.
Connecting to cluster1a.us.messagelabs.com [216.82.251.230]:25 from 107.174.26.221 ... connected
  SMTP<< 220 server-13.tower-555.messagelabs.com ESMTP
  SMTP>> EHLO mailserver.elatomo.com
  SMTP<< 250-server-13.tower-555.messagelabs.com says EHLO to 107.174.26.221:46132
         250-STARTTLS
         250-PIPELINING
         250 8BITMIME
  SMTP>> STARTTLS
  SMTP<< 220 2.0.0 continue
  SMTP>> EHLO mailserver.elatomo.com
  SMTP<< 250-server-13.tower-555.messagelabs.com says EHLO to 107.174.26.221:46132
         250-PIPELINING
         250 8BITMIME
  SMTP>> MAIL FROM:<***@countryclub.do>
  SMTP>> RCPT TO:<***@totalbank.com>
  SMTP>> DATA
  SMTP<< 250 2.0.0 MAIL FROM accepted
  SMTP<< 421 Service Temporarily Unavailable
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == ***@totalbank.com R=dkim_lookuphost T=dkim_remote_smtp defer (-44) H=cluster1a.us.messagelabs.com [216.82.251.230]: SMTP error from remote mail server after RCPT TO:<***@totalbank.com>: 421 Service Temporarily Unavailable

0

Mail server blocked by Messagelabs

January 17, 2018, 3:48 pm

≫ Next: Connections to messagelabs.com

≪ Previous: MessageLabs blocking emails error 501

$

0

0

I need a solution

I am having issues with one of my domains being blocked by messagelabs, this particular domain has mails services by Google apps and we are unable to send or receive emails to clients whose using symantec connect. When ever we try to send out an email or of the client of ours whose with Symantec tries to send out an email to us. Messagelabs keeps rejecting our emails. Can someone please guide me through the process involved  resolve this, as this keeps affecting our work.

0

Connections to messagelabs.com

January 18, 2018, 1:54 pm

≫ Next: Symantec™ Secure Email – For iOS® smart card support?

≪ Previous: Mail server blocked by Messagelabs

$

0

0

I need a solution

We received report from our zix server stating our SMTP connection to mail53.messagelabs.com is not connected. What could be the cause of this?

0

Symantec™ Secure Email – For iOS® smart card support?

January 25, 2018, 3:31 pm

≫ Next: 553 SPF (Sender Policy Framework) error G Suite

≪ Previous: Connections to messagelabs.com

$

0

0

I need a solution

Does the Symantec™ Secure Email – For iOS® support smart cards such as CAC and PIV?

0

553 SPF (Sender Policy Framework) error G Suite

January 26, 2018, 6:33 am

≫ Next: Blacklisted IP - connection timed out

≪ Previous: Symantec™ Secure Email – For iOS® smart card support?

$

0

0

I need a solution

Recieving this error bounce back sending email to a client, using G Suite with valid SPF and DKIM records what needs to happen to get this sorted?

553 SPF (Sender Policy Framework) domain authentication fail. Refer to the Troubleshooting page at http://www.symanteccloud.com/troubleshooting for more information. (#5.7.1)

0

---

Blacklisted IP - connection timed out

January 29, 2018, 6:24 am

≫ Next: Emails from our domain blocked by several companies using Symantec cloud

≪ Previous: 553 SPF (Sender Policy Framework) error G Suite

$

0

0

I need a solution

Hi,

we are trying to deliver some emails to some addresses that are hosted on a mail server protected by your service.

We have our mail server logs full of this errors:

mail postfix/smtp[370]: 3A80013BB9D: to=<xxxxx@xxxxxx>, relay=none, delay=56203, delays=56053/0.03/150/0, dsn=4.4.1, status=deferred (connect to cluster6.us.messagelabs.com[216.82.249.212]:25: Connection timed out) 

If we try to connect to your server from outside the mail server the response is successfull, so the ip address must have been blacklisted somewhere.

Our mail server IP is: 207.154.209.118 (mail.18months.it). We are not blacklisted on any list I could check.

Can you please verify, and unblock us?

Thanks

0

Emails from our domain blocked by several companies using Symantec cloud

January 31, 2018, 7:35 am

≫ Next: DNS Issue

≪ Previous: Blacklisted IP - connection timed out

$

0

0

I need a solution

We are having emails from our domain blocked by several other companies using Symantec cloud.

Have checked the link provided by Symantec support but none of our MX records are showing as being blocked - how up to date is this?

We are clear on all other spam databases.

What is the process for getting whitelisted?

Marvin

0

DNS Issue

February 1, 2018, 8:58 am

≫ Next: Blacklisted ip?

≪ Previous: Emails from our domain blocked by several companies using Symantec cloud

$

0

0

I need a solution

We are not customers of Messagelabs however we are receiving noticaiton from people trying to email our domain cardfactory.co.uk that they are receiving bounceback messages from messagelabs becuase you have tried to deliver the message to greatbritishcards.co.uk

Can you please update your DNS cache as we are not receiving emails because of this aged record.

0

Blacklisted ip?

February 2, 2018, 9:31 am

≫ Next: Blacklisted IP

≪ Previous: DNS Issue

$

0

0

I need a solution

Hi,

My client isn`t able to send any emails to a client of yours. 

Reason: Remote host said: 421 Service Temporarily Unavailable

my clients domain is rightguard.co.uk

mail server ip: 91.142.134.132

your clients mail ip:

10	cluster3.eu.messagelabs.com	194.106.220.35 MessageLabs Limited (AS21345)	4 hrs	Blacklist Check      SMTP Test
10	cluster3a.eu.messagelabs.com	85.158.139.103 MessageLabs Limited (AS21345)	4 hrs	Blacklist Check      SMTP Test

Hope someone can help. 

Thank you. 

0

Blacklisted IP

February 5, 2018, 3:04 am

≫ Next: How can i forward bluecoat proxy ASG traffic to Message labs

≪ Previous: Blacklisted ip?

$

0

0

I need a solution

Dear Sirs and Madams,

unfortunately our IP 185.185.26.140 seems blacklisted on your side. Could you please remove it from your list as soon as possbile?

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff} span.s1 {font-variant-ligatures: no-common-ligatures}

telnet cluster4.us.messagelabs.com 25

Trying 216.82.242.33...

^C

Kind Regards

0