negan07 / ancistrus

Netgear's D7000 Nighthawk Router Experience Distributed Project
https://negan07.github.io/ancistrus/
GNU General Public License v2.0
66 stars 17 forks source link

email failed 500 unrecognized command #57

Closed tominwi closed 4 years ago

tominwi commented 5 years ago

New to ancistrus having installed to my D7000 on 9-July, and every night since at 0100a when logs get emailed, the log shows many dozens of these:

[email failed] 500 unrecognized command Tuesday, July 09,2019 01:00:07

The log does get sent-out, so this is only a nuisance but I wonder if anyone here knows what about the ancistrus firmware might cause this. Of course, the Netgear firmware did not.

I have tried other email addresses/servers/settings but only one actually works to send-out the log, so I couldn't make it go away using a different set of creds.

negan07 commented 4 years ago

what is the smtp config of the working email and the other not-working ?

tominwi commented 4 years ago

The one email I have that works is a Torguard address with SMTP of mail.private-mail.com and port 465. But as I said I get dozens of those error messages in the log.

I've not been able to get any of my other email accounts to work with the Netgear, including all of Apple/icloud.com, smtp.mail.yahoo.com Port 465, smtp-mail.outlook.com Port 587, smtp.aol.com Port 587, nor mobile.charter.net or mail.charter.net which use Port 587.

negan07 commented 4 years ago

just tried a gmail account with smtp.gmail.com port 465 ssl auth enabled full working without any error message

report all the log webpage config, webpage mail config and the kind of wan connection of the router

tominwi commented 4 years ago

I thought it would be easier to just create & use a gmail account, and I did so, but it does not work at all for me. It seems my problem might have to do with my ISP but in any case since I am the only one having this problem, and the errors are only a nuisance anyway, I am going to leave well enough alone. Sorry for the distractio negan07.

negan07 commented 4 years ago

forgot to ask the firmware version even if it could be involved..

using smtpc from command line:

==========================================================
Usage: ./smtpc [m:s:f:r:h:p:U:P:cv] < files     
    -m mime type                        
    -s subject                      
    -f from addr (if NULL use recipient)            
    -r recipient                        
    -h mail server                          
    -p mail port (default=25)               
    -U user name (ESMTP)                    
    -P password  (ESMTP)                    
    -c Clear syslog                 
    -v verbose   (DEBUG)                    
========================================================

it should be possible to test the smtp email sender quickly and deeply to understand if it could be an ssl issue as it could be

negan07 commented 4 years ago

any news ?

tominwi commented 4 years ago

As your prior post was Greek to me, I defer to my earlier statement "Sorry for the distraction negan07". Do not hold-up a new release over this.