I'll throw my weight behind adding mkcert.sh to the package. The rationale is that if you google for "dovecot ssl" you'll be presented with the dovecot.org wiki pages that describe using mkcert.sh. So naturally you're going to want to try that simple approach and will fail on Ubuntu.
Simple self-signed certificates are perfectly fine in a homebrew network. When I'm out on the road, I just want an encrypted tunnel to the imap server (and smtp server) on my home network. I trust my own signed certs, so I don't need anything else. The lack of mkcert.sh in the Ubuntu package for dovecot makes life harder. -- mkcert.sh dovecot-openssl.cnf https://bugs.launchpad.net/bugs/59642 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
