On Tue, Feb 28, 2012 at 7:51 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
All,
Why does the new dovecot package move the dovecot.conf to dovecot.conf.pacsave? The same 2.0 configuration works with 2.1, why leave the user without any dovecot.conf at all?
[2012-02-27 15:17] warning: /etc/ssl/dovecot-openssl.cnf saved as /etc/ssl/dovecot-openssl.cnf.pacsave [2012-02-27 15:17] warning: /etc/dovecot/dovecot.conf saved as /etc/dovecot/dovecot.conf.pacsave [2012-02-27 15:17] upgraded dovecot (2.0.18-1 -> 2.1.1-3)
Why not a just a warning that:
warning: basic configuration options have been updated, see: http://wiki2.dovecot.org/BasicConfiguration
-- David C. Rankin, J.D.,P.E.
Was just coming here to ask similar. As far as I can understand, this is so the user can use their own (unaffected by upgrades) dovecot.conf, but we have /etc/dovecot/local.conf which is by default enabled in the stock dovecot.conf anyway for that.