I'm wondering if anyone else has seen the following log messages when trying to configure Notifications using GMail (email address have been obfuscated but everything else was left alone):
Apr 4 10:15:03 Jingleheimer-NAS postfix/cleanup: EE9D2461ABD: message-id=<20200404141503.EE9D2461ABD@Jingleheimer-NAS.local>Apr 4 10:15:03 Jingleheimer-NAS postfix/qmgr: EE9D2461ABD: from=<firstname.lastname@example.org>, size=459, nrcpt=2 (queue active)Apr 4 10:15:04 Jingleheimer-NAS postfix/pipe: EE9D2461ABD: to=<email@example.com>, relay=omvnotificationfilter, delay=0.08, delays=0.03/0.02/0/0.03, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)Apr 4 10:15:04 Jingleheimer-NAS postfix/smtp: connect to smtp.gmail.com[2607:f8b0:400d:c01::6c]:587: Network is unreachableApr 4 10:15:04 Jingleheimer-NAS postfix/smtp: SSL_connect error to smtp.gmail.com[188.8.131.52]:587: -1Apr 4 10:15:04 Jingleheimer-NAS postfix/smtp: warning: TLS library problem: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:332:
Some other tidbits:
- Clean install of OMV 5.3.9 (installed using the OMV ISO)
- The sending email ("firstname.lastname@example.org" above) has 2-factor turned on so I am using an App Password instead of my normal authentication
- I get the same log message in another installation of OMV 5 in a VM running on my desktop (but same network)
- I doubt my local firewall is blocking SMTP traffic as I am using the same email / configuration to send notifications with other services (i.e. Shinobi, running on a different device but same network, is able to successfully send SMTP emails without issue)
- IPv6 is showing as disabled under the Network UI for the network interface and I believe its disabled in my router as well.
- I've tried limiting the Postfix SSL version with "smtp_tls_protocols=!SSLv2,!SSLv3" in /etc/postfix/main.cf following another forum post about SSLv3 being insecure. No luck.
I'm struggling to figure out what is cause and what is effect in the log messages. I suspect its a postfix SSL library issue but the "Network is unreachable" could also be the culprit rather then effect. Any ideas?