On 2/7/20 10:07 am, Benny Pedersen wrote:
Jeremy Ardley skrev den 2020-07-01 06:50:
local mail.example.com { protocol imap { ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_key = </etc/letsencrypt/live/mail.example.com/privkey.pem
service imaps_login { inet_listener imaps { address=mail.example.com }
not using hostname here, it should be either ipv4 or ipv6 not hostname
That makes maintenance difficult. postconf is helpful because it looks up the IP from the hostname each time the service is started. The issue is it looks up IPv6 in preference/exclusion to IPv4
inet_listener imap { address=mail.example.com
does this make sense for ssl ? :=)
Yes, clients can connect on port 143 (imap) but negotiate TLS. Thunderbird checks port 143 first when scanning a server for TLS connections.