With USE=ssl set dovecot 1.2.6 does much less than one could expect by simply setting 2 non exsisting paths to the 'ssl_cert_file=' and 'ssl_key_file=' directives in dovecot.conf and totally leave out the fact the package actually have it's own script and configuration files to create certificates for imaps and pop3s. These files are simply deleted, possibly due to the maintainer missed their location at doc/mkcert.sh and doc/dovecot-openssl.cnf so they go when the dir is dumped. I think they should be included if the ssl use flag is set, and they could probably be stored in /etc/dovecot (unless there is some other obvious location for it). However, either mkcert.sh also need to be sed'ed (as per default certs are created as '/etc/ssl/certs/dovecot.pem' and '/etc/ssl/private/dovecot.pem') to match path ebuild set for ssl_cert_file and ssl_key_file directives, or paths in dovecot.conf changed to the ones used by mkcert.sh - where the latter probably is the easier solution. Reproducible: Always Steps to Reproduce: 1. USE flag ssl is set 2. #emerge dovecot 3. As is now it simply creates the annoyance the dovecot server will error even when doing a trival util task as dumping all non-default configuration items and exit (dovecot -n). So if not completing the job, comment out the ssl directives in dovecot.conf
Thank you for the bug report. dovecot-1.2.11-r1 is in the tree which should solve this problem. Please close the bug if it does.
it appears to be ok now, thanks.
