Yes, I just hit this problem too.
My config was pointing to my own certificate and was changed to point to
the self-signed cetificate.
I'm not quite sure what is the intended purpose of the following code in
postinst?
OLD_SSL_CERT="/etc/ssl/certs/dovecot.pem"
OLD_SSL_KEY="/etc/ssl/private/dovecot.pem"
.....
if [ -e $OLD_SSL_CERT ] || [ -e $OLD_SSL_KEY ]; then
echo "You already have ssl certs for dovecot."
echo "However you should move them out of /etc/ssl"
echo "and into /etc/dovecot and update the configuration"
echo "in /etc/dovecot/conf.d/10-ssl.conf accordingly."
echo "See /usr/share/doc/dovecot-core/NEWS.Debian.gz for details."
perl -i -nE "
if (/^\w*?ssl_cert/) {
say 'ssl_cert = <$OLD_SSL_CERT'
}
elsif (/^\w*?ssl_key/) {
say 'ssl_key = <$OLD_SSL_KEY'
} else {
print;
}" /etc/dovecot/conf.d/10-ssl.conf
First, why should you ever modify the conf file at all? And without
informing the user and without keeping a backup?
And why do this just because dovecot's generated certificate files
happen to exist?
Thanks,
Gedalya
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
