The problem with the flow of mail messages from the server 141.105.65.33 When you try to send an email, you get the answer "501 Connection rejected by policy [7.7] 9504, please visit www.messagelabs.com/support for more details about this error message". Can we find out about the reasons?
Hi,
Having a valid URL in the email containing encoding of special characters in the parameter of the URL e.g. %2F, will result in below Click-time URL.
https://clicktime.symantec.com/a/1/C0wv3lbDolkuNfSupOJp3P8xaadEbLTclU6XnduaqBo=?d=4z70XHCj7cpIYpa1umVY5H7J5rqp32gUhGyVLniLOtpNFX3p7Q2Knxo63ke1kuerU8JGG-bwExZg2KkCy2uw3ENu08D91Z2Y_qsG5USEyWMyG9DgSXJJzaKwoSJ-c--iCo0iAzLh1YTAHwlNTsWmlUFpE_VTOrRo6zS6glZCYVJvJXFwquV62D74WnC7AmFZxcvFyRpltcZo9QwD-872FYCIyYvTOvNd5bZB4f4fl9_P7EPI_5uEcK6B5pxMPwadER1sUzXVa9TH_nGnV8rxNHiJiPy7Y9CXSFIjrkd6yYMnuLkXdcrhnv2lLr9synpS0yZIMOeaMyFSqxFGOK9WgynzP81-uWWJpCPYOPVCycms9jdLapZpcb5LJeagijq0-nk0oq-GjT2E63rsKOm-6pOuLdkZ6RGQNZTCt7IYbCIgHp6vzuzKtaGqzcCs71S4qIRQu_87u5rSVbCK01gD7NzVxwdvzUeldWuLq3tKGzq4aBdshEueRKdd_B5p&u=https%3A%2F%2Fxxxxxxxxxxxxxxxxxxxxxx.com%2TRACK%2Fexternal%2Fdownload%3Fq%3D163334d25b97aa7596a919cac654db2171f7f7c32uaWAjdhh11toDgMfv3R6dxNIxHlCu%2FB8mOMm6ZhNtXs18tC6kIjZXxlVgRhpt0%2BxGFNoaPmqBKMIJqjf8gTCjgiXqkinnC%2Bw%2B66NLt8tFVwT5NIC%2Fim0mBgqeSeeIKWjVlEAcnXxsUEUZqBHg8toDIGL6eR3CF0B9MWLgFvx4W9Tp1JXdbgP1J4pRwwoDYyQL7ou46sLfL%2FF9u3j4O%2FK98sggPpUX09wlq2neUqchFGbYtxq3Jp6JpYFV%2B5RiiwEew5oSt5Bb7DFaT8NpgPP7LnP6nAV4c7kPGemo8%2B5ojCRsjwbVcrfKJQA1RvOaf
Click-time maintains the encoding correctly up to this stage.
However, after calling this URL, the Symantic redirect reverts the encoding of the entire Click-time u parameter including the parameter q in the origingal URL. This results in an invalid URL containing e.g. / in the parameter.
/TRACK/external/download?q=163334d25b97aa7596a919cac654db2171f7f7c32uaWAjdhh11toDgMfv3R6dxNIxHlCu/B8mOMm6ZhNtXs18tC6kIjZXxlVgRhpt0+xGFNoaPmqBKMIJqjf8gTCjgiXqkinnC+w+66NLt8tFVwT5NIC/im0mBgqeSeeIKWjVlEAcnXxsUEUZqBHg8toDIGL6eR3CF0B9MWLgFvx4W9Tp1JXdbgP1J4pRwwoDYyQL7ou46sLfL/F9u3j4O/K98sggPpUX09wlq2neUqchFGbYtxq3Jp6JpYFV+5RiiwEew5oSt5Bb7DFaT8NpgPP7LnP6nAV4c7kPGemo8+5ojCRsjwbVcrfKJQA1RvOaf
From my view, this should be technically avoidable from Symantec side by maintaining the encoding of the original URL parameter.
As currently all URLs are breaking, fast help would be very much appreciated.
Many thanks,
Matt
Hello,
I got the return email message from cluster8.eu.messagelabs.com, the message is connection timed out.
I tried to check if our email server has a negative reputation from http://ipremoval.sms.symantec.com/lookup/.
And the reply is below.
The IP address you submitted, 60.251.126.92, does not have a negative reputation and therefore cannot be submitted for investigation.
May I know how to solve the problem?
Then our email server can communicate with server cluster8.eu.messagelabs.com without problems.
Best Regards,
Alex
I am having trouble sending individual e-mails and getting the following bouce back :
host cluster2.eu.messagelabs.com [85.158.136.51]
SMTP error from remote mail server after end of data:
553-SPF (Sender Policy Framework) domain authentication
553-fail. Refer to the Troubleshooting page at
553-http://www.symanteccloud.com/troubleshooting for more
553 information. (#5.7.1)
I have checked that the SPF and DKIM records are correct.
The outgoing servers don't have a problem.
The recipient e-mail address is correct
I am trying to reply to an email (have managed to go do vis gmail but this is not a long term solution)
I have checked that our domain is not on any Spam blacklists.
Would it be possible for someone to look into this:
The IP is: 185.119.175.252
Hi we are running a mailserver on 149.210.163.35. Message we are receiving from mailservers which are using messagelabs is: Cannot delivered, host not available. When using an other ip, it works. So we expect that our IP is on a blacklist. However that is not the case, please help to support us.
We checked our IP: The IP address you submitted, 149.210.163.35, does not have a negative reputation and therefore cannot be submitted for investigation.
kind regards,
Bas
We had an IP address listed on the messagelabs reputation list. This IP was not listed on ANY other blacklist. The IP has since been removed from your blacklist, but we are unable to send mail to customers using your filters. Our IP address is 138.201.136.178.
Can you please look into this - we've got hundreds of mail in our queues.
Hello,
since a few days ago we have problems sending mail to a client. We received a rejection with the following message:
Remote Server returned '<cluster3.eu.messagelabs.com # 5.0.0 smtp; 501 Connection rejected by policy [7.7] 14012, please visit www.messagelabs.com/support for more details about this error message.> '
At first, our IP 142.4.15.61 had a negative reputation at http://ipremoval.sms.symantec.com/lookup/ but not anymore.
Our IP does not appear in any blacklist.
How can we solve this?
Thanks for your time and help
HI all, sorry for my poor english!
I try to send mail to one domain protected by symantec, their IT told me that, one single address is blacklisted (only one user in my organization, other users can send at the same recipient)
Using the tool at this page: http://ipremoval.sms.symantec.com/lookup/ i had verified by myself the address, is not listed but marked as "neutral"
How can i request delisting for single user "user@company.com" and not for all "@company.com" or IP/Subnet?
More details i prefer to share via PVT message if needed.
Thanks
Hi
I run a mailserver for a couple of clients.
Outbound to one of their contacts who is using messagelabs is failing
telnet to port 25 of the messagelabs servers from my mailserver mail.dataskill.co.uk 31.193.136.55 although I can telnet in from other IPs
It could be down to incorrect SPF records for my clients domains but these have now been corrected
nt@ls1:~$ telnet 85.158.136.35 25
Trying 85.158.136.35...
telnet: Unable to connect to remote host: Connection timed out
TIA
Nick
Is there anyway to test and ensure that the TLS enforcement configured between business partner domain and my domain is working? What happens if an email is sent from the business partner without using TLS?
Hello,
2 of our customers have problems sending mails messagelabs.com servers.
When we look in the Exchange queue viewer we always see an error “4.2.1 Service temporarily unavailable”.
We have checked the IP-addresses on http://ipremoval.sms.symantec.com/lookup/ but they’re not listed. We also checked on mxtoolbox.com.
How can we solve this problem ?
IP-address customer 1 : 84.199.77.2
IP-address customer 2 : 81.82.255.131
As part of the DigiCert acquisition of Symantec’s Website Security and related PKI solutions, our digital certificates will now be issued by the DigiCert public certificate authority. We expect to issue all new public TLS certificates from this hierarchy starting from November 28, 2017.
For more information, go to article INFO4722 and read how this change affects the Email Security.cloud service.
If you need further assistance or have additional questions, contact Symantec Technical Support.
Good Morning,
We not be able to send messag to all email addres that use messagelabs.com.
We are not in black list and our domain, hugotrumpy.it is correctly configured.
Please help us urgently.
se below an exsample of the errors:
====================================================================
= Greetings from the MDaemon mail system at htmail.hugotrumpy.it = ====================================================================
The following message:
Session-ID: 546330 (specific to this delivery attempt)
Queue-ID: pd90000003330.msg
Message-ID: 004b01d369a9$7096d900$51c48b00$@hugotrumpy.it
has not (as yet) been delivered to the following recipient(s):
despite one or more unsuccessful attempts to do so.
Delivery attempts will continue for up to 48 hours (2 days). If delivery fails after that time you will be separately informed.
You do not need to resend the message!
The original message headers follow at the end of this report. For information on DSN messages see http://www.altn.com/dsn/.
Please quote the Queue-ID, Session-ID, and Message-ID found above in any inquiries regarding this message.
========================
= Session Transcript =
========================
Session 546330; child 0004
Parsing message <xxxxxxxxxxxxxxxxxx\pd50000693451.msg>
* From: gr.pandi@hugotrumpy.it
* To: hongkong@londonpandi.com
* Subject: GLORY HONGKONG
* Size (bytes): 9363
* Message-ID: <004b01d369a9$7096d900$51c48b00$@hugotrumpy.it>
* Route slip host: londonpandi.com
* Route slip port: 25
Resolving MX record for londonpandi.com (DNS Server: 192.168.1.151)...
* P=010 S=000 D=londonpandi.com TTL=(60) MX=[cluster3.eu.messagelabs.com]
* P=020 S=001 D=londonpandi.com TTL=(60) MX=[cluster3a.eu.messagelabs.com]
Attempting SMTP connection to cluster3.eu.messagelabs.com
Resolving A record for cluster3.eu.messagelabs.com (DNS Server: 192.168.1.151)...
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.137.67]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.137.83]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.136.3]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.139.3]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.136.35]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[194.106.220.35]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[85.158.137.35]
* D=cluster3.eu.messagelabs.com TTL=(5) A=[194.106.220.51]
Randomly picked 194.106.220.35 from list of possible hosts
Attempting SMTP connection to 194.106.220.35:25
Waiting for socket connection...
* Socket error 10060 - The connection timed out.
* 194.106.220.35 added to connection failure cache for 5 minutes
Attempting SMTP connection to cluster3a.eu.messagelabs.com
Resolving A record for cluster3a.eu.messagelabs.com (DNS Server: 192.168.1.151)...
* D=cluster3a.eu.messagelabs.com TTL=(5) A=[85.158.139.103]
Attempting SMTP connection to 85.158.139.103:25
Waiting for socket connection...
* Socket error 10060 - The connection timed out.
* This message is 65 minutes old; it has 0 minutes left in this queue
Remote queue lifetime exceeded; message placed in retry queue
========================
= End Transcript =
========================
We have been experiencing email delay issues to Messagelabs.com recipient addresses for 2 months. Only Messagelabs, no other recipients. We have had our customers open tickets with Symantec to try and resolve the issue. We have supplied verbose SMTP logs to Symantec both via tickets and here on the Forums. Each time, Syamntec stops responding as soon as the evidence shows this isn't a quick fix and possibly a Symantec issue. We have log evidence that shows our email server (only 1 sending IP address that is clean with Symantec) will make a good TLS connection to a Messagelabs.com tower and 20 minutes later it fails to the same tower. Messagelabs will drop all new connections with a "ConnectionReset" timeout. Always 4 minutes after we send our SSL cert to them.
Symatnec states that they are not throttling our traffic, but all evidence looks like they are. On Mondays, our email traffic goes with little to no delay. By Tuesday, mid-morning, delays start to build from 2-4 hours. Overnight, our queses clear up. The next day, the delays build faster and last longer. By Friday, we still have email from Thursday in our outbound queue. Over the weekend, when we are not sending mail, the queues clear and we have no problems sending again on Monday AM.
Becasue we are not a Symantec customer ourselves, we can't directly open a ticket. We have had to rely on our customers to act as a middleman to Syamntec each time and then Symantec even stops responding to them. Could I PLEASE, get a response from a Symantec Engineer who can spend a little time to resolve the issue. We are not the first person to post about the same email delays. Even if it requires a configuration change on our end, many others will benefit from knowing what messagelabs is looking for to make routine good connections.
Hopefull for a response,
-Bob Scott, Network Admin, Laddawn MFG.
Good day,
We are unable to send mail from our servers to absa.co.za. Our servers are spamserver1.innovateit-cloud.co.za 129.232.150.227, spamserver2.innovateit-cloud.co.za 129.232.150.228
>
>A few of our customers that's using our hosted exchange server are having difficulties sending mail to overseas clients. The error message that comes back gives a timeout error. One example is fleetman@absa.co.za<mailto:fleetman@absa.co.za>. I have had a few complaints that no mails can be send to absa.co.za.
>
>Regards,
>
>Luke
>
>
> host cluster3a.eu.messagelabs.com [85.158.139.103]
> SMTP error from remote mail server after RCPT TO:<fleetman@absa.co.za>:
> 421 Service Temporarily Unavailable: retry timeout exceeded
>
>This message was created automatically by mail delivery software.
>A message that you sent has not yet been delivered to one or more of
>its recipients after more than 24 hours on the queue on spamserver1.innovateit-cloud.co.za.
>
>The message identifier is: 1eJgHQ-0008Ix-Ok
>The subject of the message is: FW: Inward Transfer Notification - Reference Number: [DQC52136287]
>The date of the message is: Tue, 28 Nov 2017 13:48:15 +0000
>
>The address to which the message has not yet been delivered is:
>
> tris@absa.co.za<mailto:tris@absa.co.za>
> host cluster3a.eu.messagelabs.com [85.158.139.103]
> Delay reason: SMTP error from remote mail server after RCPT TO:<tris@absa.co.za<mailto:tris@absa.co.za>>:
> 421 Service Temporarily Unavailable
>
>No action is required on your part. Delivery attempts will continue for
>some time, and this warning may be repeated at intervals if the message
>remains undelivered. Eventually the mail delivery software will give
>up, and when that happens, the message will be returned to you.
>
>From: Mail Delivery System
><Mailer-Daemon@spamserver1.innovateit-cloud.co.za<mailto:Mailer-Daemon@
>spamserver1.innovateit-cloud.co.za>>
>Date: 30 November 2017 at 01:37:40 SAST
>To: <tessa@bmgortho.com<mailto:tessa@bmgortho.com>>
>Subject: Warning: message 1eJbv1-000F7b-3n delayed 24 hours This
>message was created automatically by mail delivery software.
>A message that you sent has not yet been delivered to one or more of
>its recipients after more than 24 hours on the queue on spamserver1.innovateit-cloud.co.za<http://spamserver1.innovateit-cloud.co.za>.
>
>The message identifier is: 1eJbv1-000F7b-3n
>The subject of the message is: Re: TEST
>The date of the message is: Tue, 28 Nov 2017 09:09:09 +0000
>
>The address to which the message has not yet been delivered is:
>
> Christopher.Hughes@wright.com<mailto:Christopher.Hughes@wright.com>
> host cluster5a.us.messagelabs.com<http://cluster5a.us.messagelabs.com> [216.82.251.230]
> Delay reason: SMTP error from remote mail server after RCPT TO:<Christopher.Hughes@wright.com<mailto:Christopher.Hughes@wright.com>>:
> 421 Service Temporarily Unavailable
>
>No action is required on your part. Delivery attempts will continue for
>some time, and this warning may be repeated at intervals if the message
>remains undelivered. Eventually the mail delivery software will give
>up, and when that happens, the message will be returned to you.
Dear,
we are a germany located hosting company and detected that one of our ips is on your private blacklist.
cluster8.eu.messagelabs.com #<cluster8.eu.messagelabs.com #4.0.0 smtp; 501 Connection rejected by policy [7.7] 18008, please visit www.messagelabs.com/support for more details about this error message.> #SMTP#The given url is not available. I found via google the ip removal tool of symantec but it says our ip is not listed.
Please check if our ip is blacklisted: 144.76.214.48
Kind regards,
Holger Schramm
Network Administrator
Hola,
desde hace unos días tenemos problemas para enviar correos a un cliente.Recibimos un rechazo con el siguiente mensaje:
El servidor remoto devolvió '<cluster3.eu.messagelabs.com # 5.0.0 smtp;501 Conexión rechazada por política [7.7] 14012, visite www.messagelabs.com/support para obtener más detalles sobre este mensaje de error.
Al principio, nuestra IP 142.4.15.61 tenía una reputación negativa en http://ipremoval.sms.symantec.com/lookup/ pero ya no.
Nuestra IP no aparece en ninguna lista negra.
¿Cómo podemos solucionar esto?
Gracias por tu tiempo y ayuda
Bonjour,
Nous rencontrons un probleme avec vos passerelles antispam depuis notre serveur exchange.
Tous les domaines relayés vers vos serveurs messagelabs.com sont rejetés :
Voici un exemple :
RecipientStatus : {[{LED=421 Service Temporarily Unavailable};{MSG=};{FQDN=cluster1a.eu.messagelabs.com};{IP=85.158.139.103};{LRT=30/11/2017 14:46:02}]}
Nous ne sommes blacklisté nul part pourtant.
voici l'ip de notre serveur : mailhost.ac-environnement.com, 93.95.238.172
Pouvez vous remedier a ce probleme dans les plus brefs delais ?
Merci par avance
Cdt
C.LAURENT
Hello,
Our emails sent by our clients at midsouthtransport.com are getting delivery error "501 Connection rejected by policy [7.7]. I have checked and our server IP address 162.144.39.143 and it is not blacklisted. The client does use SpamExperts.com and I can see that one of their IP addresses lastmx.spamexperts.net IP 209.58.136.65 IS blacklisted by BACKSCATTERER but since that is a program designed to protect from spam in incoming emails and not outgoing emails I don't know why it would affect our server reputation or cause a problem getting emails to Messagelabs.net clients.
The bounce back messages look like this:
-----Original Message-----
From: Mail Delivery System [mailto:Mailer-Daemon@server.dennisvberwyn.com]
Sent: Friday, December 01, 2017 3:01 PM
To: sandyl@midsouthtransport.com
Subject: Mail delivery failed: returning message to sender
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:
Tita_Rivera-Lim@apllogistics.com
host cluster6.us.messagelabs.com [216.82.241.100]
SMTP error from remote mail server after initial connection:
501 Connection rejected by policy [7.7] 22011, please visit
www.messagelabs.com/support for more details about this error message.
Neil_Ma@apllogistics.com
host cluster6.us.messagelabs.com [216.82.241.100]
SMTP error from remote mail server after initial connection:
501 Connection rejected by policy [7.7] 22011, please visit
www.messagelabs.com/support for more details about this error message.
IFS_LCL_imports@apllogistics.com
host cluster6.us.messagelabs.com [216.82.241.100]
SMTP error from remote mail server after initial connection:
501 Connection rejected by policy [7.7] 22011, please visit
www.messagelabs.com/support for more details about this error message.
The clients sent a request to investigate the issue about a week ago and we haven't heard anything yet. I checked here on Symantec and our server is not blacklisted by Symantec. This is affecting their business.
Please advise?
Mia McPherson
We now have a number of clients reporting that emails to the Office 365 / Exchange Online service that have message labs in the loop, are being marked as Phishing.
We have seen this on our own setup as well.
No one seems to be taking it seriously and I can't beleive that no one else is seeing this. We even have on-premise Exchange clients, sending via Message Labs to non ML protected EOP clients going in as phishing.
I think someone needs to take a good look at this.
Thanks,
Mike
