NTP does seem to be working as does the Astro Binding.
Just getting back to tinkering with the system after 6 months…no need to since it has worked fine.
So need to get my mind around things again.
Since I want to add a Zwave device to my network in a few days, I figured I’d get things working before trying H3…
see the documentation Mail - Bindings | openHAB
Sounds like your configuration for the security is set to PLAIN. You should set it to STARTTLS to not submit the password in plaintext.
Depending on how you upgraded there will be an upgrade.log file where you can go back and see that stuff that flew by.
This is from FireMotD which is not part of openHAB. It is what generates that table of machine statistics when you first log in. Sometimes it gets messed up. You can usually fix it by running that command it tells you to run from the FireMotD folder (/opt/firemotd perhaps?).
By default Astro will “discover” a sub and moon thing based on the lat/long configured in settings. I assume something similar is going on with NTP, it discovered an NTP service on your network.
The security parameter defines the transport security and can be set to PLAIN (default), STARTTLS or SSL (for implicit SSL/TLS). The port parameter is used to change the default ports for the SMTP server. Default ports are 25 (for PLAIN and STARTTLS) and 465 (for SSL).
So it shouldn’t be port 25 that is mentioned in the log, right ?
What if you use the keyword SSL instead of TLS ? Does it work then ?
Yes, indeed it does. But, I have no idea why with the setting as TLS the log mentions port 25.
I changed the setting to STARTTLS and it now appears to be working.
Because the SMTP connection starts on that port. It is plaintext per default then starts encrypting after STARTTLS is issued but the port stays to be 25.