On 1. Jul 2026, at 15.11, Patrick Cernko via dovecot <dovecot@dovecot.org> wrote:
Hi Dovecot Devs,
I'm currently setting up Dovecot 2.4 as frontend proxy to our backends. The frontends simply use an LDAP attribute of the user to connect to the assigned IMAP backend server. That works fine so far.
According to the documentation <https://doc.dovecot.org/2.4.4/core/man/doveadm-kick.1.html>, I should be able to disconnect a user with
doveadm kick USERNAME
or all sessions to a specific backend with
doveadm kick -h BACKEND_IP
or simply ALL sessions with
doveadm kick '*'
However the command reports the expected amount of connections kicked and exitcode 0, but all sessions stay connected. I also tried 'doveadm proxy kick ...' but as the the corresponding documentation states, this is only an alias for 'doveadm kick ...' and thus shows the same behavior.
Looks like kicking proxied connections works only in login processes' "high performance mode": https://doc.dovecot.org/2.4.4/core/config/login_processes.html#high-performa...
I'll get it fixed for the default "high security mode" as well, hopefully for v2.4.5 still.
On 1. Jul 2026, at 15.11, Patrick Cernko via dovecot <dovecot@dovecot.org> wrote:
Hi Dovecot Devs,
I'm currently setting up Dovecot 2.4 as frontend proxy to our backends.
The frontends simply use an LDAP attribute of the user to connect to the
assigned IMAP backend server. That works fine so far.
According to the documentation
<https://doc.dovecot.org/2.4.4/core/man/doveadm-kick.1.html>, I should
be able to disconnect a user with
doveadm kick USERNAME
or all sessions to a specific backend with
doveadm kick -h BACKEND_IP
or simply ALL sessions with
doveadm kick '*'
However the command reports the expected amount of connections kicked
and exitcode 0, but all sessions stay connected. I also tried 'doveadm
proxy kick ...' but as the the corresponding documentation states, this
is only an alias for 'doveadm kick ...' and thus shows the same
behavior.
Looks like kicking proxied connections works only in login processes' "high performance mode": [1]https://doc.dovecot.org/2.4.4/core/config/login_processes.html#high-performa... I'll get it fixed for the default "high security mode" as well, hopefully for v2.4.5 still.
References
Visible links