> On Nov 28, 2016, at 2:13 PM, rich.gre...@hushmail.com wrote:
>
> # TLS parameters
> smtpd_tls_loglevel = 1;
If that ';' is really there, get rid of it.
> smtpd_tls_cert_file=/etc/letsencrypt/live/example.com/fullchain.pem
> smtpd_tls_key_file=/etcletsencrypt/live/example.com/privkey.pem
The key file setting seems to have a typo.
> smtpd_use_tls=yes
The non-obsolete setting is: "smtpd_tls_security_level = may"
> smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
Not recommended, let TLS session tickets do the work.
> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
This one is fine.
> I sent a test message from squirrelmail to myself, and it worked.
"It worked" is meaningless. Was TLS used? Is that sent via port 587 or
port 25? Logs?
> I tried with Thunderbird, and it had a problem.
Was this via port 25 or 587?
> Sending of the message failed.
> An error occurred while sending mail: Unable to establish a secure link with
> Outgoing server (SMTP) example.com using STARTTLS since it doesn't advertise
> that feature. Switch off STARTTLS for that server or contact your service
> provider.
Did it even contact the same server? The obfuscated "example.com" is not
terribly
helpful.
Perhaps you're better of with mailinabox.email, rather than DIY?
--
Viktor.
