Skip to main content
NetApp Knowledge Base

Set ASUP SMTP authentication failure with URL using bad/illegal format or missing url

Views:
33
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport (ASUP)

Issue

  • Set AutoSupport SMTP authtication server failure with "using bad/illegal format or missing URL ".


cluster::>autosupport modify -node *  -mail-host user1@email.demo.com

Enter password for remote host "email.demo.com":

Enter password for remote host "email.demo.com" again:

 

Warning: SMTP connectivity check failed for destination: user1:********@email.demo.com.  Error:  URL using bad/illegal format or missing URL
 
  • Notifyd section shows the same failure reason.

00000017.0005855f 0018ffc9 Thu Mar 07 2024 10:06:13 +08:00 [kern_notifyd:info:1942] 0x80e572500: 0: ERR: AutoSupport::StatusCheck: Connectivity check to SMTP Mail Host cht:********@mail.cii_encrypt/ZXGpqzuzse7c8bQP74472RLKHdilT2y5RU/aNLTOQMk=/cii_encrypt destination                                        failed. Reason: URL using bad/illegal format or missing URL
00000017.00058560 0018ffc9 Thu Mar 07 2024 10:06:13 +08:00 [kern_notifyd:info:1942] 0x80e572500: 0: ERR: AutoSupport::StatusCheck: URL rejected: Malformed input to a URL function

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.