A few weeks ago I missed a friend's birthday. Then I saw that I had not gotten any mails from my home server for a couple of days - and since I use bdrem to get notified about birthdays by mail, they did not reach me.
My mail server showed the following error:
postfix/smtpd: connect from cafe.dip0.t-ipconnect.de[126.96.36.199] postfix/smtpd: SSL_accept error from cafe.dip0.t-ipconnect.de[188.8.131.52]: -1 postfix/smtpd: warning: TLS library problem: error:140940F5:SSL routines:SSL3_READ_BYTES:unexpected record:s3_pkt.c:1456: postfix/smtpd: lost connection after STARTTLS from cafe.dip0.t-ipconnect.de[184.108.40.206] postfix/smtpd: disconnect from cafe.dip0.t-ipconnect.de[220.127.116.11]
There was no specific bug to find about that error message, and I noticed that the last commit was made 2011, 5 years ago. Things changed quite a bit since then; SSLv2 and SSLv3 are considered unsafe now and have been disabled on my server. My guess is that ssmtp does not support TLS and thus fails.
Instead of reporting a bug to an apparently unmaintained package and waiting for it to be fixed, I looked for an alternative.
Previously I used the following config for ssmtp:
firstname.lastname@example.org mailhub=mail.example.org hostname=bogo.home.example.org FromLineOverride=YES AuthUseremail@example.com AuthPass=password UseTLS=yes UseSTARTTLS=yes
dma uses two config files, one for basic configuration and one for credentials. Adjusting the sample config file shipped with dma works fine:
SMARTHOST mail.example.org AUTHPATH /etc/dma/auth.conf SECURETRANSFER STARTTLS MAILNAME /etc/mailname