Skip to main content
NetApp Knowledge Base

Not receiving AutoSupport e-mails from ONTAP due to 550 5.7.1 Unable to relay

Last Updated:

Applies to

  • ONTAP 9
  • SMTP
  • AutoSupport


NetApp controllers are unable to relay AutoSupport e-mails to external e-mail addresses, including autosupport using an SMTP mailhost server

Similar Error messages:

  • message: 550 5.7.1 Unable to relay
  • READMSG:554 Mail from rejected for policy reasons
  • message: Access denied: 550
Check Autosupoprt History
  • Cluster::>autosupport history show

             Seq                                    Attempt  Percent  Last
Node         Num   Destination Status               Count    Complete Update
------------ ----- ----------- -------------------- -------- -------- --------
node01      1680   smtp        transmission-failed  15       -        5/28/2020 02:20:53


  • Use the "system autosupport history show -seq-num ### -instance" command to review the specific sequence and the Last Error is Failed sending data to the peer.  

Cluster::> system autosupport history show -seq-num 1680 -instance

                            Node: node01
     AutoSupport Sequence Number: 1680
Destination for This AutoSupport: smtp
                   Trigger Event:
             Time of Last Update: 5/28/2020 02:20:53
              Status of Delivery: transmission-failed
               Delivery Attempts: 15
             AutoSupport Subject: MANAGEMENT_LOG
                    Delivery URI:
                      Last Error: Failed sending data to the peer  
              Time of Generation: 5/28/2020 00:01:51
     AutoSupport Compressed Size: 131.4KB
                Percent Complete: -
                  Rate of Upload: -
       Time Remaining for Upload: 0s
   AutoSupport Decompressed Size: 476.0KB
      Total Collection Time (ms): 6257

The detailed error messages can be determined by viewing the errors logged by notifyd.log  in the AutoSupport subsystem by reviewing the /mroot/etc/log/mlog/notifyd.log or by reviewing your organization's Mailhost logs.

How to review notifyd.log

Run command
::> node run -node (node name) -command rdfile /etc/log/mlog/notifyd.log

Example output:

(emittime: 8/6/2017 01:16:27) (message: RCPT TO:<>)
(emittime: 8/6/2017 01:16:27) (message: SMTP 0x8115ae810 state change from MAIL to RCPT)
(emittime: 8/6/2017 01:16:32) (message: 550 5.7.1 Unable to relay)


(emittime: 7/7/2017 05:10:31) (message: DO phase starts)
(emittime: 7/7/2017 05:10:31) (message: MAIL FROM:<>)
(emittime: 7/7/2017 05:10:31) (message: SMTP 0x812b31810 state change from STOP to MAIL)
(emittime: 7/7/2017 05:10:31) (message: 554 Mail from rejected for policy reasons.)


(emittime: 3/11/2015 10:11:58) (message: Access denied: 550)


(emittime: 12/3/2021 16:57:10) (message: MAIL FROM:<
(emittime: 12/3/2021 16:57:10) (message: SMTP 0x80a708940 state change from STOP to MAIL)
(emittime: 12/3/2021 16:57:10) (message: STATE: DO => DOING handle 0x80bd5a008; line 1344 (connection #0) )
(emittime: 12/3/2021 16:57:10) (message: 530 5.7.1 Authentication required)
(emittime: 12/3/2021 16:57:10) (message: MAIL failed: 530)
(emittime: 12/3/2021 16:57:10) (message: DO phase failed)
(emittime: 12/3/2021 16:57:10) (message: Curl_done)
(emittime: 12/3/2021 16:57:10) (message: Marked for [closure]: SMTP done with bad status)
(emittime: 12/3/2021 16:57:10) (message: QUIT)
(emittime: 12/3/2021 16:57:10) (message: SMTP 0x80a708940 state change from MAIL to QUIT)
(emittime: 12/3/2021 16:57:10) (message: 221 2.0.0 Bye)
(emittime: 12/3/2021 16:57:10) (message: SMTP 0x80a708940 state change from QUIT to STOP)
(emittime: 12/3/2021 16:57:10) (message: Closing connection 0)


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.