Skip to main content
NetApp Knowledge Base

Failed to send AutoSupport via SMTP with error 553 5.7.1 "Sender address rejected: not logged in"

  1. Last updated
  2. Save as PDF
Views:
28
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport
  • Transport SMTP

Issue

  • Failed to send AutoSupport due to an error Failed sending data to the peer 

autosupport_history.xml

                             Node: node-01
      AutoSupport Sequence Number: xxx
 Destination for This AutoSupport: smtp
                    Trigger Event: callhome.invoke.all
              Time of Last Update: x/x/xxxx xx:xx:xx
               Status of Delivery: transmission-failed
                Delivery Attempts: 15
              AutoSupport Subject: USER_TRIGGERED(ALL:node-01_NetApp_Test_Alert)
                     Delivery URI: mailto:autosupport@netapp.com
                       Last Error: Failed sending data to the peer　
               Time of Generation: x/x/xxxx xx:xx:xx

  • Check for the following error notifyd.log: 

[kern_notifyd:info:2478] (category: 2478:159:deliver) (message: 553 5.7.1 myemail@company.com: Sender address rejected: not logged in)
[kern_notifyd:info:2478] (category: 2478:159:deliver) (message: RCPT failed: 553)

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.