Skip to main content
NetApp Knowledge Base

Can username contain @ mark in configuring authentication to smtp server for ASUP transferring?

Views:
931
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9.5 or earlier

Answer

  • The AutoSupport  mail-hosts parameter supports authentication using the user:password@mailhost format.
  • However, if an email address is used as the user name, the @ symbol in the email address is misinterpreted as the mailhost name and the parameter is not parsed correctly.

For example: autosupport modify -node node1 -mail-hosts user1@host.com:pw1@mailhost1host.com is interpreted as the mailhost name.

  • As a workaround, in the user name, enter %40 instead of the @ symbol.

For example: autosupport modify -node node1 -mail-hosts user1%40host.com:pw1@mailhost1

Additional Information

  • BUG 851157
  • username and password pair setting is not available via System Manager GUI. Please use CLI instead and refer to the following docs below.
    • ONTAP 9.5 or earlier : system node autosupport modify
      [-mail-hosts <text>,…​] - SMTP Mail Hosts
      Also, you can optionally prepend a user name and password combination for authentication to each mail server.
      The format of the username and password pair is user1:pw1@mymailhost.example.com .<-----------------
      The username and password can be specified on none, all, or some of the mail hosts.
    • ONTAP 9.6 or later : system node autosupport modify
      [-mail-hosts <text>,…​] - SMTP Mail Hosts
      Also, you can optionally prepend a user name and password combination for authentication to each mail server.
      The format of the username and password pair is user1@mymailhost.example.com . <-----------------
      User will be prompted for the password. <-----------------
      The username and password can be specified on none, all, or some of the mail hosts.

 

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.