i use a prette old routerboard (rb112) for monitoring serial connected an USV.
the script checks every minute the state. - when some threshold exceeds the board
should send an email. - since i have upgraded to 3.30 the mail-sending mechanism doesnt
any more working.
i found out there is TLS implemented. - since i dont like creating an certificate (cpu load etc)
i wondering if there is an simple way to disable TLS on the RB? (since the mailserver advertises
TLS)
Chris, please clarify your issue. Post us screenshot as well.
Sergejs - show a screen shot of what?
Steger is correct, I am using a Linux box for my mail server and have RBs all around the world sending email via a mail server. Now that ROS 3.30 uses TLS the RBs seem to want to answer the mail server query with requesting tls service for smtp… I use smtp-auth on, in my case, port 587, I don’t use tls for my auth port (587), nor do I want to start.
Anyway - since ROS 3.30 no emails are being processed from the RBs. All my (mail server) logs show that the RBs request tls, and since I don’t support tls on port 587, the server (my mail server) discconnects the RBs.
Basically the issue are;
Most of us use smtp-auth on a particular port for email from RBs.
Many of us do not use tls (for various reasons).
ROS 3.30 insists on using TLS to send email to a server - anyone that has a mail server that does not (use or support tls) can no longer send email from an RB with ROS 3.30.
We’s like to see this fixed. It (smtp-auth) worked fine in ROS 3.24
The last I read the new userman is still in beta, and I am still seeing several posts regarding issues with it. So until userman is stable under ROS 4.x then I won’t be switching the couple of units that are the base Usermanagers for a couple networks over to ROS 4.x
