NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Email alert does not work @ RAIDiator 4.2.21
I've attempted to configure email alert to a couple of recipients, but I can't get it to work using the built-in, nor the gmail mail engine. The /var/log/exim/mainlog lists this after attempting to...
Finally I got it to work!!! :D
While flipping & turning every stone on the NAS's harddrive I finally stumbled on this log file:
/var/log/frontview/msmtp.log
Each time when using the gmail engine, the following was logged:
Sep 14 13:08:33 host=smtp.gmail.com tls=on auth=on user=bla.bla@bla.bla from=bla.bla@bla.bla recipients=bla.bla@bla.bla smtpstatus=535 smtpmsg='535-5.7.1 Username and Password not accepted. Learn more at\n535 5.7.1 http://support.google.com/mail/bin/answ ... swer=14257 somehash errormsg='authentication failed (method LOGIN)' exitcode=EX_NOPERM
I then found another file that stores the email account settings when using anything but the internal engine:
/etc/msmtprc
All looked good, but my 20+ years of experience of UNIX troubleshooting made me wonder if a blank space in my email password could cause trouble?
After trying to escape it (\) and embrace the setting with quotes, etc. I resorted to change my email password and eliminate the space character...
Voila...
Ergo: RAIDiator 4.2.21 is unable to properly submit alerts if the email account password contains a space character. It even corrupts password containing space characters once the settings are "reapplied". If you touch some other setting, e.g. a recipient name (leaving the hidden, bullet formatted password unchanged) and push "Apply" the password will now be "chopped" after the first space character.
Still, I wonder why the built-in email engine (exim) does not "find its way out of the box"?
It would have been very nice to be able to skip the gmail settings leaving my dear password in plain text on my NAS drive.
/f
While flipping & turning every stone on the NAS's harddrive I finally stumbled on this log file:
/var/log/frontview/msmtp.log
Each time when using the gmail engine, the following was logged:
Sep 14 13:08:33 host=smtp.gmail.com tls=on auth=on user=bla.bla@bla.bla from=bla.bla@bla.bla recipients=bla.bla@bla.bla smtpstatus=535 smtpmsg='535-5.7.1 Username and Password not accepted. Learn more at\n535 5.7.1 http://support.google.com/mail/bin/answ ... swer=14257 somehash errormsg='authentication failed (method LOGIN)' exitcode=EX_NOPERM
I then found another file that stores the email account settings when using anything but the internal engine:
/etc/msmtprc
All looked good, but my 20+ years of experience of UNIX troubleshooting made me wonder if a blank space in my email password could cause trouble?
After trying to escape it (\) and embrace the setting with quotes, etc. I resorted to change my email password and eliminate the space character...
Voila...
Ergo: RAIDiator 4.2.21 is unable to properly submit alerts if the email account password contains a space character. It even corrupts password containing space characters once the settings are "reapplied". If you touch some other setting, e.g. a recipient name (leaving the hidden, bullet formatted password unchanged) and push "Apply" the password will now be "chopped" after the first space character.
Still, I wonder why the built-in email engine (exim) does not "find its way out of the box"?
It would have been very nice to be able to skip the gmail settings leaving my dear password in plain text on my NAS drive.
/f
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
