The problem is that on already-configured dovecot installations there is
a chance that the dovecot-postifx.conf will not work out-of-the-box. I
am sure that for *new* installations of dovecot the provided d-p.conf
will work fine -- but this is not to be expected for existing installs.
But ideally -- on existing & customised dovecot installs --, the new
configuration should be installed as -- say -- dovecot-
postfix.conf.dpkg.inst, or similar, giving time for the system
maintainer to check and adjust as needed.
The newly-installed d-p.conf was broken, for me:
1. replaced my SSL certs by a default SSL cert;
2. disabled SSL client authentication;
3. reset user name formatting to the default (u...@realm, instead of just
username);
4. disabled MD5 authentication.
These are small changes, but the result was -- for example -- the loss
of all Evolution mail filters for all clients, since nobody could
connect to IMAP anymore.
If, instead, the new dovecot configuration was created *without* being
set active (and a warning given that dovecot-postfix integration was not
yet active), I would have had time to adjust, check & set the
integration without causing any users any pain.
I have since reinstalled dovecot-postifx, but now I knew the install was
going to be broken, so I took the necessary care.
If no such option (*not* to blindly replace existing dovecot
configuration) can be be provided, then at least the installation
procedure should provide an option to be cancelled.
** Changed in: dovecot (Ubuntu)
Status: Incomplete => New
--
dangerous action: dovecot-postfix force-installs new conf file
https://bugs.launchpad.net/bugs/339966
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
