NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

JoergA22's avatar
JoergA22
Aspirant
May 14, 2022

R8500 Nighthawk with Firmware V1.0.2.158 fails sending notification e-mail

My Nighthawk R8500 with firmware V1.0.2.158 has been configured to send notification e-mails, but it fails sending the mails.

Log-entry:  "[email failed] Bad sequence of commands, Saturday, May 14,2022 13:01:00"

Already check for newer firmware which fixes the problem - but no update available.

The SMTP-Mailserver requires authentication and TLS-encryption. Is this not supported by the R8500? Are there any restrictions for the password (though it is accepted ...)?

5 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    May 14, 2022

    What Browser are you using?

    What email services are you using? 

    How is the email server on the router configured? Auto or Specific port? 

     

    Was a factory reset and setup from scratch performed after the FW was updated? 

    "Already check for newer firmware which fixes the problem - but no update available." <No sure what this means here.

    • JoergA22's avatar
      JoergA22
      Aspirant
      May 14, 2022

      Thanks for taking your time to look into this problem.

      What browser do I use? => I'm using Microsoft Edge, today it's Version 101.0.1210.39, but sometimes I'm using Google Chrome.

      What email service do I use? => It's ionos.de, very common in Germany

      How is the email client on the router configured?

      - 2 Destination Mail-addresses (our mailbox for IT-services and additionally my personal mailbox)

      - the appropriate SMTP server (smtp.ionos.de)

      - Specific Port 587 (as required by the mail-server, not Auto-detect, though Auto-detect found this port too)

      - Mail server requires authentication

      - username and password as defined for the mail-account on the mail-server (a specific mail-account for the Nighthawk)

      Was a factory reset and setup from scratch performed after the FW was updated? => Yes, in fact, because a firmware-update was not possible without a factory reset

      "Already check for newer firmware which fixes the problem - but no update available." <No sure what this means here => I've checked whether the installed firmware is the latest version and verified that no newer version is available yet.