Email Security.cloud

 View Only
  • 1.  Emails blocked - Connection rejected by policy [7.7]

    Posted Dec 07, 2017 01:32 PM

    We are currently being blocked by Message labs.

    I submited an investigation here: https://support.symantec.com/en_US/article.TECH82881.html almost 12 hours ago with no reply.

    I have checked mxtoolbox & symantec's blacklist checks and we are not black listed.

    I have also attempted to phone Symantec support however they can't raise a case as I'm not a symantec customer.

    Example logs:

    Dec  7 00:45:04 mx1 postfixpool_1/smtp[11065]: 4D5FF7CF1ED: to=<Roger.Milton@moore-scarrott.co.uk>, relay=cluster5.eu.messagelabs.com[193.109.254.3]:25, delay=25705, delays=25704/0.5/0.14/0, dsn=4.0.0, status=deferred (host cluster5.eu.messagelabs.com[193.109.254.3] refused to talk to me: 501 Connection rejected by policy [7.7] 18405, please visit www.messagelabs.com/support for more details about this error message.)

    Dec  6 00:18:49 mx1 postfixpool_1/smtp[47437]: E6D467CF660: to=<Roger.Milton@moore-scarrott.co.uk>, relay=cluster5.eu.messagelabs.com[85.158.138.179]:25, delay=25578, delays=25578/0.04/0.35/0, dsn=4.0.0, status=deferred (host cluster5.eu.messagelabs.com[85.158.138.179] refused to talk to me: 501 Connection rejected by policy [7.7] 16909, please visit www.messagelabs.com/support for more details about this error message.)

    I URGENTLY need this issue resolved as we have over 40 companies that can't send emails through our spam protection system at the moment.

    Please advise the quickest way to get this issue resolved and also to find out why we are being blocked to ensure we can prevent this from happening again.

    We are currently working on bringing up another mailhost and transfering the mail queue onto a new host with a new IP however future emails will still come into this IP.



  • 2.  RE: Emails blocked - Connection rejected by policy [7.7]

    Posted Dec 08, 2017 06:48 PM

    This issue is still not resolved.

    I can't raise a case with symantec as I'm not a symantec customer.

    How do I proceed with getting this issue resolved?