Messaging Gateway

 View Only
  • 1.  554 5.7.1 You are not allowed to connect

    Posted Mar 31, 2016 12:58 AM

    People,

    My client is reporting that they can send any email to my domain but not receiving any reply back or even NDR / rejection report.

    When the client let say CompanyX try to email us it goes through without any bounce back on their end. When I check our Messaging gateway (Symantec Brightmail) and scan for the past week, but I cannot see our gateway being hit with their emails

    CompanyX IT provided the below trace and the interesting part is this connection error “554 5.7.1 You are not allowed to connect.

    I have added *@CompanyX.net as a good sender/whitelisted in the appliance.

    Your help and advice is appreciated.

    Thank you



  • 2.  RE: 554 5.7.1 You are not allowed to connect
    Best Answer

    Broadcom Employee
    Posted Mar 31, 2016 01:18 AM

    do you see the error in the logs?

    can you check if this information helps?

    https://support.symantec.com/en_US/article.TECH93644.html



  • 3.  RE: 554 5.7.1 You are not allowed to connect

    Posted Mar 31, 2016 01:25 AM

    Which log do you mean Pete ?



  • 4.  RE: 554 5.7.1 You are not allowed to connect

    Broadcom Employee
    Posted Mar 31, 2016 02:02 AM

    Message Audit log or the NDR information?



  • 5.  RE: 554 5.7.1 You are not allowed to connect
    Best Answer

    Posted Mar 31, 2016 02:17 AM

    Usually this error is triggered by filter policy static-opl, which means the sending IP is on the symantec global black list.

    Check your host-logs for the connecting IP.

    Searching the message audit log filtering on eg recipient wont get you anything because the connection is terminated earlier.

    Thomas

     



  • 6.  RE: 554 5.7.1 You are not allowed to connect
    Best Answer

    Posted Apr 01, 2016 06:36 AM

    hi,

     

    many people enabled more spamfilter options in the last weeks, i saw.

    locky could be a reason why ;-)

     

    did you enable "dns-validation" on the scanner's?

    are the mx records in the public DNS of the companyx.net correct?

     

    i enabled dns-validation on our scanners last week, some senders got this message, too.

    the reason was that the sending server had an other ip as in MX-record's fieds in the public-dns of the company.

    dns-validations checks this and they got a 554 error.

    and senders can't be whitlisted against dns-validating. there is no option to bybass this.

     

    regards,

    eurass

     



  • 7.  RE: 554 5.7.1 You are not allowed to connect

    Posted Apr 04, 2016 06:31 PM

    Yes, you guys are correct. The IP address is black listed by Symantec for the domain.

    I have forwarded the screenshot to the sender IT department so they can request it for taking it out.

    Thanks guys.