Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


older | 1 | .... | 20 | 21 | (Page 22) | 23 | 24 | .... | 42 | newer

    0 0
  • 06/14/17--23:30: 553 Message filtered.
  • I need a solution

    Hi,

    I send a mail to 'CLOUDfeedback@feedback-87.brightmail.com' yesterday, with some false positive mails attached.

    When sending mails to customers, who we regularly stay in touch with, we keep receiving this 553 error.

    It just suddenly started to happen. We haven't made any changes to our setup, so i really don't understand why we suddenly gets these errors?

    We really need to be able to send mails to our customers, so is it possible that you will take a look at the mail i send you guys yesterday?

    I send the mail from rsc@egn.com.

    Really need this fixed today!

    Best Regards

    Rasmus Schiødt

    0

    0 0

    I need a solution

    I run a clean, no-spam email server, but I continue to get blocked by messagelabs for various unexplained reasons. My server is on no major blacklists and has been running on this IP since last September.

    This is getting extremely frustrating for both myself and for my customers.

    The IP address is: 162.250.120.146.

    The messages for various senders on my servers to various recipients over the past 10 days include:

    501 Connection rejected by policy [7.7] 16307 from sender domain battlefieldroofing.com for recipient domain petersenmail.com
    501 Connection rejected by policy [7.7] 4605 from sender domain battlefieldroofing.com for recipient domain metalera.com
    501 Connection rejected by policy [7.7] 15103 from sender domain epiphanychurch.net for recipient domain pnc.com
    501 Connection rejected by policy [7.7] 9416 from sender domain battlefieldroofing.com for recipient domain petersenmail.com
    501 Connection rejected by policy [7.7] 4306 from sender domain saintann-parish.com for recipient domain jpmorgan.com
    501 Connection rejected by policy [7.7] 4004 from sender domain saintann-parish.com for recipient domain jpmorgan.com
    501 Connection rejected by policy [7.7] 4011 from sender domain saintann-parish.com for recipient domain jpmorgan.com
    501 Connection rejected by policy [7.7] 20905 from sender domain onlinemarketingguild.com for recipient domain stvincents.org

    This is way out of a hand. Please help.

    0

    0 0

    I need a solution

    Several of our customers and suppliers use messagelabs and are unable to send or receive email from our domain (thesolution.co.uk) consitstently. They are receiving the generic 553 message. Our SPF and DKIM records are intact, and mail is coming from legitimate accounts.

    We have tested what messages can get through and it appears to be linked to the e-mail address of the sender being part of our standard signature.

    Once we removed the e-mail address from the signature we appear to be able to send, but the customer then receives the error when attempting to reply.

    This seems to be a problem with the content triggering the filtering.

    We have checked that we are not listed on any blacklists either ip based or domain based.

    Can you please explain how we can identify the problem.

    0

    0 0

    I need a solution

    Several of our customers and suppliers use messagelabs and are unable to send or receive email from /to our domain (thesolution.co.uk) consitstently.

    They are receiving the generic 553 message. Our SPF and DKIM records are intact, and mail is coming from legitimate accounts and IP Addresses.

    We have tested what messages can get through and it appears to be linked to the e-mail address being part of the standard signature.

    Once we removed the e-mail address from the signature we appear to be able to send, but the customer then receives the error when attempting to reply.

    This seems to be a problem with the content triggering the filtering.

    We have checked that we are not listed on any blacklists either ip based or domain based.

    Replies to the customer with their e-mail signatures contained their e-mal address also fails with erro 553.

    Can you please explain how we can identify the problem.

    0

    0 0

    I need a solution

    Hello, 

    could you please clear our IP from the blacklist? 
    89.200.172.75

    Some of our customers get this message when trying to send a mail :(

    Best regards from Austria, 
    Stefan T. 

    0

    0 0

    I need a solution

    I am trying to find the latest due dilligence type reports for Symentec Email.Cloud. I am a member of their Customer Trust Portal but the docs there are every old - Some CenturyLink, Saavis, and Terramark docs dated 2012, 2013. Anything newer? I did email privacy@symantec.com and DL-IT-CustomerTrustOffice@symantec.com back on 5/31 and did not receive a reply.

    https://www.symantec.com/connect/groups/customer-trust-portal

    Thanks for any help anyone can provide.

    0

    0 0
  • 06/19/17--23:23: Blacklist Removal
  • I need a solution

    Dear Sir,

    Our Server IP 202.130.87.248 had been blocked from you. Would you remove our IP from your blacklist and let us send out the messages?

    Thanks!
    William

    0

    0 0
  • 06/20/17--02:05: Full IP blocks listed?
  • I need a solution

    Dear Symantec,

    It seems that almost our whole AS-number is listed.
    The AS-number is as47869.

    In particulair 94.228.208.0/20, 109.235.48.0/21, 178.239.48.0/20, 31.171.128.0/22, 37.46.192.0/22.
    Is it possible to get these delisted, or let us know the exact reason so we can take actions to make sure it gets delisted again?

    Thank you in advance.
    Kind regards. 

    0

    0 0

    I need a solution

    Hi,

    I'm trying to send an email to a messagelabs.com address but unfortunately it's being rejected. This is from the logs:

    Jun 20 12:00:34 melkor postfix/qmgr[780]: 106FF1D4: from=<XXX>, size=1266, nrcpt=1 (queue active)
    Jun 20 12:01:04 melkor postfix/smtp[3072]: connect to cluster3.eu.messagelabs.com[85.158.136.35]:25: Connection timed out
    Jun 20 12:01:34 melkor postfix/smtp[3072]: connect to cluster3.eu.messagelabs.com[194.106.220.51]:25: Connection timed out
    Jun 20 12:02:04 melkor postfix/smtp[3072]: connect to cluster3.eu.messagelabs.com[85.158.139.3]:25: Connection timed out
    Jun 20 12:02:34 melkor postfix/smtp[3072]: connect to cluster3.eu.messagelabs.com[85.158.137.35]:25: Connection timed out
    Jun 20 12:03:04 melkor postfix/smtp[3072]: connect to cluster3.eu.messagelabs.com[85.158.136.3]:25: Connection timed out
    Jun 20 12:03:04 melkor postfix/smtp[3072]: 106FF1D4: to=<XXX>, relay=none, delay=150, delays=0.09/0.01/150/0, dsn=4.4.1, status=deferred (connect to cluster3.eu.messagelabs.com[85.158.136.3]:25: Connection timed out)

    Ths server I am using is a VPS which I know has had spam sent from it in the past (judging by the number of blocklists I had to be removed from), but it should be clean now. Could someone have a look?

    This is my server:
    melkor.jcowgill.uk.2209INA185.145.46.63
    melkor.jcowgill.uk.3156INAAAA2a07:4580:b0d:7b9::1

    Thanks,
    James

    0

    0 0

    I need a solution

    Hola buenos días.

    Tenemos el siguiente problema. La semana pasada estábamos en una lista negra de dominios y no podíamos enviar correos. Rellenamos el formulario de baja en cuestión y actualmente no aparecemos en ninguna lista negra.

    Nos han llamado de 3 empresas diferentes, indicando que no reciben nuestros correos. Investigando, hemos comprobado que los 3 dominios, utilizan los servidores messagelabs, por lo que rogamos por favor, si pueden revisar las listas de bloqueos para quitarnos y solventar el problema. Hemos comprobado en el siguiente foro https://www.symantec.com/connect/forums/blacklist-removal-messagelabscom-connection-rejected-policy#comment-11761311 que podemos estar en una lista negra histórica.

    Hemos comprobado nuestros registros MX, SPF, DKIM y todo está correcto, es más, a otros dominios los cuales no utilizan los servidores messagelabs no tenemos ningún problema en el intercambio de correos.

    Nuestros dominios son:

    imf.com                                   

    imf-formacion.om                    

    Los dominios afectados son:

    aramark.es         cluster1.us.messagelabs.com

    caixabank.com cluster4.eu.messagelabs.com

    ferrovial.com    cluster3.eu.messagelabs.com

    Esperamos su respuesta.

    Muchas gracias.

    Un saludo.

    0

    0 0

    I need a solution

    I have an email system on IP: 188.165.166.129

    My users and I have been getting some mails returning with: "501 Connection rejected by policy [7.7]"

    The server is not black listed, implements DKIM, and on http://ipremoval.sms.symantec.com/lookup/ it reports:

    "The IP address you submitted, 188.165.166.129, does not have a negative reputation and therefore cannot be submitted for investigation."

    Could you please check why this address is getting blocked?

    Thanks,

    0

    0 0
  • 06/21/17--08:14: Rule through the DL
  • I need a solution

    Hello Team

    In our environment we get many requests to block the sender address.is there any way we can create the DL which will be sync with AD and I can give access to user to add and remove sender address from the DL. Rather than having them reach out to us on a daily basis. If yes how can we achieve this.

    0

    0 0

    I need a solution

    Dear sirs

    It's almost a couple of weeks that I found every day our mail server listed in your blacklist with a bad reputation, only in your.

    Each day I request an investigation at http://ipremoval.sms.symantec.com/lookup/ and the problem seems to be resolved till the next day. The reason provided for the assessment is:

    The IP address 137.74.69.100 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.

    but this message cannot apply to our server because we don't send spam and I take care that it does not happen.

    I verified also the meaning of "Snow Shoe Spam" and I have created a ticket on OVH support to solicit a verification of IP closer to our subnet but this isn't an acceptable reason to block our IP.

    This issue is costing to our company a lot of problems and money because our customers send email to important company, like Banks, Insurance Company etc that use your mail security platform and they see often rejected their emails with blacklist reason.

    In this day we received two domain transfer request by our ex-customers for this email issue, an economic damage of about $1000/year for your issue.

    There is no spam coming out from our mail server, there is no virus on our mail server, no other pc in our network is sending spam nor is infected, no pc of our customers is infected, no pc of our customers can send viruses through our server, every abuse about spam from our customes is immediately detected and locked.

    To be sure of my statements I verified our mail server analyzing logs in depth and no spam coming out in the past weeks.

    Please keep in mind that our mail server is not listed in any worldwide blacklist but only in your one and the IP reputation of our mail server is good in other worldwide services.

    Would you please help me to solve this problem forever?

    Thank you in advance

    Kind regards

    Umberto Celentano

    P.S.: the screenshot attached to this message is related to another SMTP used only by web server. The main mail server of my company is mercur.netfly.it and the IP address is listed above. Please I prefer to maintain this IP private so I really appreciate if you can obfuscate or delete it from this message before make it public.

    0

    0 0
  • 06/22/17--00:43: Timeouts
  • I need a solution

    Hello,

    In the past, one of our customer's mailserver got compromised and then you blocked it somehow, this may be the reason why connections from MTA to MTA get timeouts. 

    The customers server in question is: v1002.lhisp.com

    Can you please tell me why there is a timeout?

    Best regards

    0
    1498123550

    0 0
  • 06/22/17--06:12: Email being blocked
  • I need a solution

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

    Hi we are having all outbound email going via MessageLabs blocked.

    I saw IP 212.110.177.249 has landed on a list somewhere. It has been removed.

    The IP 212.110.177.249 resolves to our web host, IT HAS NOTHING TO DO WITH EMAIL.

    We use Office 365, Mimecast, SPF, DKIM, we are pretty current with best practices etc. Then we get listed for something one of many website users might have done on our webhost of choice? This IP is not ours, it is not controlled by us, and to be listed for it needs explaining.

    Yes SHKF.co.uk resolves to the Web IP. But why not check the MX record? The IP was removed 7 hours ago, and we are in our third day of disruption.

    Can you fix this please

    David

    0

    0 0

    I need a solution

    Hello,

    we have a new IP from our Datacenter for one Server.
    The Customers on the Server cant send Mails to "messagelabs".

    Please Remove ASAP the IPs 173.212.234.48 and 2a02:c207:3002:389::1

    Thanks a lot.

    Greetings from Germany

    Jay

    0

    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:

    AD053E1804B0    15556 Thu Jun 22 17:04:22  i**@n****.es
    (host cluster4a.eu.messagelabs.com[216.82.251.230] said: 421 Service Temporarily Unavailable (in reply to RCPT TO command))
                                             s***o@ca****nk.com

    Our IP is 62.210.209.202 and it is not blacklisted.

    If it is temporary like your error sugests how long will it take to heal itself?

    Thanks in advance for any help/advice it would be much appreciated.

    Kind Regards

    Xabier

    0

    0 0

    I need a solution

    Hi,

    We have a problem delivering mail to Messagelabs.

    Our sending mail server is clean and not delivering spam, cross checked twice.

    We already checked also your reputation service at the following addresss and reported that our IP is clean:

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

    Can you please remove any block from this IP?

    Server IP:

    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}

    212.83.171.144

    Still we are experiencing the following errors:

    "action=delayed reason=connect to cluster5.eu.messagelabs.com[85.158.136.83]:25: Connection timed out"

    "action=delayed reason=connect to cluster5.eu.messagelabs.com[193.109.255.99]:25: Connection timed out"

    Thanks in advance for your collaboration.

    0

    0 0

    I need a solution

    Hello,

    I am the administrator of  innovation-matrix.com mail server running behind a public ip of 166.63.122.124

    Recently two of our major customers failed to receive our company emails.

    They are both using messagelabs.com services.

    After looking at the SMTP server log files, we came accross the issue of 

    2017-06-22 22:31:51 [51706] 1dNr7G-00093c-RO == jdurham@appliedrobotics.com<JDurham@appliedrobotics.com> R=dkim_lookuphost T=dkim_remote_smtp defer (-44) H=cluster5a.us.messagelabs.com [85.158.139.103]:25: SMTP error from remote mail server after RCPT TO:<JDurham@appliedrobotics.com>: 421 Service Temporarily Unavailable

    Please advice what can be the source of such an issue and if there was a penalty at this IP, please remove it from your databases.

    Thanks in advance

    0

    0 0
  • 06/23/17--08:32: Mails are blocked
  • I need a solution

    Hello,

    we have some Issues to send Mails to "MessageLabs".
    Please review the IP: 173.212.234.48 and 2a02:c207:3002:389::1

    refused to talk to me: 501 Connection rejected by policy [7.7]

    0

older | 1 | .... | 20 | 21 | (Page 22) | 23 | 24 | .... | 42 | newer