Skip to main content
NetApp Knowledge Base

Not receiving AutoSupport e-mails from Data ONTAP due to relaying issues on mailhost

  1. Last updated
  2. Save as PDF
Views:
1,694
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

Applies to

  • Clustered Data ONTAP
  • Data ONTAP 7- Mode
  • SMTP
  • AutoSupport

Issue

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

Similar Error messages:

  • message: 550 5.7.1 Unable to relay
  • READMSG:554 Mail from user@domain.com rejected for policy reasons
  • message: Access denied: 550
Check Autosupoprt History
  • >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 "autosupport history show -seq-num ### -instance" command to review the specific sequence and the Last Error is Failed sending data to the peer.  

Node> system autosupport history show -seq-num 1680 -instance

                            Node: node01
     AutoSupport Sequence Number: 1680
Destination for This AutoSupport: smtp
                   Trigger Event: callhome.management.log
             Time of Last Update: 5/28/2020 02:20:53
              Status of Delivery: transmission-failed
               Delivery Attempts: 15
             AutoSupport Subject: MANAGEMENT_LOG
                    Delivery URI: mailto:autosupport@netapp.com
                      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

>rdfile /etc/log/mlog/notifyd.log

Example output:

(emittime: 8/6/2017 01:16:27) (message: RCPT TO:<autosupport@netapp.com>)
(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)

or

(emittime: 7/7/2017 05:10:31) (message: DO phase starts)
(emittime: 7/7/2017 05:10:31) (message: MAIL FROM:< user@domain.com>)
(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  user@domain.com rejected for policy reasons.)

or

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

 

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.