Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: skyeci on September 03, 2017, 09:42:59 AM
-
Hi
Hope someone can help please. My sd card failed in my pi3 so after installing a new on and starting from scratch I find I cannot get alerts to work from my pi3 using dsl stats.
I have tested the pi3 using ssmtp module and it can send out messages using the same settings as what came from the previous config (gmail) which works fine
I also installed the libssl-dev but no luck
Event log states ssl tsendmail error.
Can anyone help please?
Thanks
-
I guess we need eric to list the dependencies required for the linux version.
-
Not sure but the other one in use seems fine. I wonder if it's something to do with the latest version of the os of the pi3? , the one at my mum's is on dsl stats 6.0.3 but the pi os is an older build. I added the same bits to the new build but still no joy.... :(
-
I thought I posted a response, but I must have forgotten to hit the Post button.
In the case of the Raspberry Pi, the only dependency (that I know of) that isn't already included in Raspbian is libssl-dev. I've got a Pi3, and when I get the time I'll have a look at this.
-
Thanks. I am on the latest image of the os for the pi3 and I have also tried the older versions of dsl stats but it doesn't work either.
Cheers
-
did you check you have libssl-dev ned?
-
Yup. Just rebuilt it again added the module but it is the same. I think it's something to do with the latest pi build tbh. My mum's one runs an older pi build which works fine.
-
I understand this now. The latest version of Raspbian is based on the latest Debian Stable (codenamed Stretch). This is the OS I use as my main system, and email alerts don't work on my system either. DSLstats uses a rather old library to support email alerts, and this doesn't function properly with Debian Stretch (and maybe not with some other systems).
I've located a newer library and got this working properly in a little test program, and I'll now start building this into DSLstats. It will take a little while but hopefully not very long.
-
Many thanks for confirming this Eric
Look forward to the fix.
Cheers
-
Just testing the email alerts in Windows and they seem broken as well. With this in even log
04 Sep 2017 21:04:09 Failed to sent email alert - TSendMail: SMTP error: SMTP::Login
???-Other undefined Status220 TLS go ahead
-
my windows 10 box is fine on the latest version of dsl stats, test emails all good.
04 Sep 2017 18:00:10 Auto snapshots taken
04 Sep 2017 21:12:23 Email alert sent: "Alert: Test alert"
-
my windows 10 box is fine on the latest version of dsl stats, test emails all good.
04 Sep 2017 18:00:10 Auto snapshots taken
04 Sep 2017 21:12:23 Email alert sent: "Alert: Test alert"
Thanks Ned googling tls error 220 gives 'authentication fail' wonder if something has changed on my server?
How are you setup Ned? I am using port 587 TLS which has worked fine until now.
-
GMail uses port 465.
-
I will try Gmail.
-
TLS ticked, port 587 on my windows and the other pi3 that still works as on older version of the PI os..
Did you remember to log into google if that's the sending account and enable
Allow less secure apps: ON
I use one gmail account for all three to send from and just change the subject header depending on which location the alert is sent from..
-
I have changed to google and getting the same error
04 Sep 2017 22:53:39 Failed to sent email alert - TSendMail: SMTP error: SMTP::Login
???-Other undefined Status
Where is the Less secure apps setting. I have changed to 465 port.
-
Login to Google, my account, connected apps and sites, Allow less secure apps: ON
In dsl stats
Tick in tls/ssl 587 works fine on my win10 box. smtp.gmail.com
Receiving account at the top.
Sending account at the bottom (my gmail one)
-
Login to Google, my account, connected apps and sites, Allow less secure apps: ON
In dsl stats
Tick in tls/ssl 587 works fine on my win10 box. smtp.gmail.com
Receiving account at the top.
Sending account at the bottom (my gmail one)
I cant see that less secure apps setting in my google account could you check?
This is the error I get with port 587
04 Sep 2017 23:07:51 Failed to sent email alert - TSendMail: SMTP error: SMTP::MailFrom
Permanent Failure-Invalid command530-5.5.1 Authentication Required. Learn more at
530 5.5.1 https://support.google.com/mail/?p=WantAuthError e10sm4382259wrh.94 - gsmtp
-
Hi
@roseway - tlsv1.0 and 1.1 I believe are classed weak and some stop using those ciphers
@banger - your error is the sending server requires credentials to send, so you have to login or pass credentials to be able to send. We use smtp auth required on enterprise class mail clusters
Another point to remember is some mail servers require a standard connection to port 25, then it's upgraded to secure prior to any credentials been passed, but I'm sorry, it has a name but I cannot for the life of me remember it sorry.
Many thanks
John
-
I cant see that less secure apps setting in my google account could you check?
The error message includes this link
https://support.google.com/mail/?p=WantAuthError
which takes you to the appropriate help.
-
All sorted now with Ned's help using Gmail. Google sent me an email asking if it was me trying to sign in with a less secure app and if I wanted I could enable less secure apps using a link in the email which I did and now it all works although why my ISPs server stopped accepting emails is a puzzle but that is a separate issue.
04 Sep 2017 23:39:24 Email alert sent: "Alert: Test alert"
-
The error message includes this link
https://support.google.com/mail/?p=WantAuthError
which takes you to the appropriate help.
I was using two step authorization that is why I couldn't see the "Use less secure apps" switch.
-
@roseway - tlsv1.0 and 1.1 I believe are classed weak and some stop using those ciphers
So I understand, but what does that actually mean in this context? The alert emails won't be carrying any confidential information, so is this any sort of security issue?
-
Hi roseway
Many thanks
Sorry, I should have been more clear sorry and mentioned it because you were updating your package
Some mail servers would only use tlsv1.2, and drop anything lower (same as when SSLv3 was dropped)
I think the majority though, would still allow tls1 or 1.1, but thought I had better mention it in case you were not aware
Lastly, tlsv1.3 is coming out of beta, but this will take time to filter into systems
I hope that helps a little and sorry if you were already aware
Many thanks
John
-
I see, thanks John.
-
I've looked into this a bit further now. The SSL library which I'm changing to supports any version of TLS, and which versions are supported in practice depends on the version of openssl which the OS uses. All versions of openssl from v1.0.1 onwards support TLS v1.2. All fairly recent versions of Linux (including Raspbian on the Raspberry Pi) should meet this requirement. I've located a source of openssl v1.0.2 for Windows, which I can package with DSLstats.
-
I will test the new openssl windows build if you want eric and test with my mail server, PM me if you want me to before releasing it. :)
-
Thanks Chrys, it will take a few days.