On Tue, Oct 02, 2007 at 11:08:33PM -0000, Ante Karamatić wrote:
> OK. Same happens with protocols = none. Ideal situation would be to
> start services which are installed. Can we change dovecot.conf during
> install of imapd|pop3d? This is already in imapd|pop3d.postinst:
>
> #perl -pi.bak -e 'if (/^\s*protocols =/i) { s/$/ imap imaps/ unless
> /imap/; };'\
> # /etc/dovecot/dovecot.conf
>
> Is this what
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204213
>
> is talking about?
>
I think so. However care should be taken not to change a user setting.
If the user set protocols to none, the post-install script should not
reenable it when upgrading the dovecot package.
On Tue, Oct 02, 2007 at 11:08:33PM -0000, Ante Karamatić wrote: postinst: dovecot. conf bugs.debian. org/cgi- bin/bugreport. cgi?bug= 204213
> OK. Same happens with protocols = none. Ideal situation would be to
> start services which are installed. Can we change dovecot.conf during
> install of imapd|pop3d? This is already in imapd|pop3d.
>
> #perl -pi.bak -e 'if (/^\s*protocols =/i) { s/$/ imap imaps/ unless
> /imap/; };'\
> # /etc/dovecot/
>
> Is this what
>
> http://
>
> is talking about?
>
I think so. However care should be taken not to change a user setting.
If the user set protocols to none, the post-install script should not
reenable it when upgrading the dovecot package.
--
Mathias