Email Security.cloud

 View Only
  • 1.  Remote Server returned '< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client.

    Posted Oct 24, 2019 08:43 PM

    We are not receiving email from a company that uses Message Labs and we use Proofpoint. We do not see the email hitting Proofpoint at all. Proofpoint does NOT require SMTP authentication.

     

    Is this a Messagelab configruation issue?

     

    Thank you!

     

     

    Here is the header info, stripped of personal data:

     

    Delivery has failed to these recipients or groups:
    MyClient@myclient.com


    A problem occurred while delivering this message to this email address. Try sending this message again. If the problem continues, please contact your helpdesk.


    Diagnostic information for administrators:
    Generating server: server-2.bemta.az-a.us-west-2.aws.symcld.net
    MyClient@myclient.com
    Remote Server returned '< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client. >'

     


    Original message headers:
    Return-Path: <TheSender@sender.com>
    Received: from [xx.yy.zz.aa] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits))
        by server-2.bemta.az-a.us-west-2.aws.symcld.net id 1C/63-27934-3AB50BD5; Wed, 23 Oct 2019 13:54:43 +0000
    X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOKsWRWlGSWpSXmKPExsUy45Bij+6i6A2
      xBkcvaVj83TiBzaJ1/zc2ByaPvkVv2QIYo1gz85LyKxJYMy7u3M5U8HUBY8W9L/+YGhhvz2Hs
      YuTiEBLYwSix7+gSti5GTiBnP6PEuY8yIDabgIPEpe37WEFsEQF3iXctTUxdjBwcwgKSEqvf+
      YKYIgJSEivv8UFUGEn86HzBBhJkki68FiTMK+Am0bPuAwuIzSggJvH91BomEJtZQFzi1p
      P5YLaEgIjEw4un2SBsUYmXj/+xQtgGEluX7mOBsBUldv75zwLRmyLx4NZ6Roj5ghInZz5hmcA
      oOAvJ2FlIymYhKYOIZ0lcnNPPDGHrSCzY/YkNwtaWWLbwNTOMfebAYyZUcQ4gO1mib3oyRFhe
      YtLP7UCtXED2MkaJjdMOQfUqSkzpfsi+gJFnFaNFUlFmekZJbmJmjq6hgYGuoaGRrqGRha6hq
      bleYpVuol5psW55anGJrpFeYnmxXnFlbnJOil5easkmRmDcphQ0zN3B+PbIa71DjJIcTEqivK
      mn1scK8SXlp1RmJBZnxBeV5qQWH2KU4eBQkuA1itwQKyRYlJqeWpGWmQNMITBpCQ4eJRHeGyB
      p3uKCxNzizHSI1ClGV44JL+cuYuY4eHQekPy4agmQ/A4m2zcCSSGWvPy8VClx3hMgzQIgzRml
      eXCjYenvEqOslDAvIwMDgxBPQWpRbmYJqvwrRnEORiVh3qgooCk8mXklcBe8AjqOCeg4Of71I
      MeVJCKkpBqYFGYYzhMUs5+t7xzGFLpItED86wSdllkNdjEG68PD4nNfpCtV/YlSVltx9v8bg/
      uZwp3aBrP6nuSd+nb2r85Fn2BJ/91P9z7+MfHBmbDSxBSDx5J8nfUsKzbZn/31R1psfv1XNc9
      aVg07ffUNr1MNp3lazf8UGMzv9vAn44+/Snu2vOe7zrp7z3Sjov9CleYTFKVYv5i2P59gPylE
      /pUdc01+pmqTR4q+XOaH8oT0GVK5dasnNijtZrkru/8c4+JdcWs+LPX4nGbobda4gX+e4Zw40
      2OnHhWoBV+9eJmLtY3Z7pDs7QOWK8T+pVjEFYr8C+/c8iXkame0PfvxdE3NOy/fT1i7Y8ccUZ
      bXM7qVWIozEg21mIuKEwHMKYbv+gMAAA==
    X-Env-Sender: TheSender@sender.com
    X-Msg-Ref: server-11.tower-331.messagelabs.com!1571838881!115107!1
    X-Originating-IP: [111.222.333.444]
    X-SYMC-ESS-Client-Auth: outbound-route-from=pass
    X-StarScan-Received:
    X-StarScan-Version: 9.43.12; banners=-,-,-
    Received: (qmail 7940 invoked from network); 23 Oct 2019 13:54:42 -0000
    Received: from ptr1.sender.com (HELO mail.sender.com) (111.222.333.444)
      by server-11.tower-331.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 23 Oct 2019 13:54:42 -0000
    Received: from SENDER-EXCH-03.SENDER.COM (111.222.333.113) by
     SENDER-EXCH-02.SENDER.com (111.222.333.112) with Microsoft SMTP Server (TLS) id
     15.0.1497.2; Wed, 23 Oct 2019 08:54:17 -0500
    Received: from SENDER-EXCH-03.SENDER.COM ([fe80::49aa:4b74:6495:96d4]) by
     SENDER-EXCH-03.SENDER.com ([fe80::49aa:4b74:6495:96d4%13]) with mapi id
     15.00.1497.000; Wed, 23 Oct 2019 08:54:17 -0500
    From: "Sender, Sender" <TheSender@sender.com>
    To: Person 1<MyClient@myclient.com>, Person 2 <SNoel@myclient.com>
    Subject: FW: Sales
    Thread-Topic: Sales
    Thread-Index: AdWJqEYIueyQsz8ypTwSTmmWe97H46wAAQ94g
    Date: Wed, 23 Oct 2019 13:54:16 +0000
    Message-ID: <363823bb7f0b4b0a8d0205f8cfa2287f@SENDER-EXCH-03.SENDER.com>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    x-ms-exchange-transport-fromentityheader: Hosted
    x-originating-ip: [10.1.10.100]
    Content-Type: text/plain
    MIME-Version: 1.0



  • 2.  RE: Remote Server returned '< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client.

    Posted Oct 25, 2019 12:19 PM

    Following this post. We are having the same issue with just one recipient.



  • 3.  RE: Remote Server returned '< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client.

    Broadcom Employee
    Posted Nov 04, 2019 05:15 PM

    That is not one of our error codes, it is most likely issued by the recipient server.

    This article lists all of our error codes: https://support.symantec.com/us/en/article.TECH246726.html

    Regards,
    Yamma



  • 4.  RE: Remote Server returned '< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client.

    Posted Nov 04, 2019 05:58 PM

    The error came from this server:

    Domain Name: SYMCLD.NET
    Registrar: MARKMONITOR INC.
    Sponsoring Registrar IANA ID: 292
    Whois Server: whois.markmonitor.com
    Referral URL: http://www.markmonitor.com
    Name Server: DNS1.MESSAGELABS.COM
    Name Server: DNS2.MESSAGELABS.COM
    Name Server: DNS3.MESSAGELABS.COM
    Name Server: DNS4.MESSAGELABS.COM
    Name Server: DNS5.MESSAGELABS.COM

    It looks like Messagelabs.com manages this domain as well as the sender's domain. The recipient's domain is managed by Blue Host. There seems to be an issue between Name Servers and resolving an MX record.

    We solved this by switching the name server for the recipient domain and it solved trying to get Message Labs/Symantec and our customer.