[Dovecot] dovecot and systemd
mhlavink at redhat.com
Thu Mar 15 15:34:32 EET 2012
dovecot supports systemd socket activation. Together with standard unit
activation (like old sysv init script), there are two ways how to
configure dovecot(only interface:port, not whole configuration). This
can result in situation where those configurations does not say the
same. Question is what should happen then?
For example, lets have dovecot configured to listen for imap(s) and lets
have systemd dovecot socket configured to listen for all protocols -
pop3(s) and imap(s). When dovecot is configured to start on boot,
systemd will start it and dovecot will listen on imap(s) ports. But when
dovecot.socket is enabled, it'll listen on pop3(s) too and when new pop3
connection comes, it'll pass it to dovecot and dovecot will serve it.
The question is: Should this happen? What exactly should happen when
dovecot.conf does not match dovecot.socket configuration?
More information about the dovecot