[Dovecot] doveadm director move behaviour

Daniel Parthey daniel.parthey at informatik.tu-chemnitz.de
Wed Aug 1 07:32:58 EEST 2012



Timo Sirainen <tss at iki.fi> schrieb:

>On 12.7.2012, at 14.14, Angel L. Mateo wrote:
>
>> 	So I have used doveadm director move <user> <backend ip> to move
>them to its "hashed" server. Although a doveadm director status <user>
>now shows me that this user is directed to the new server, doveadm who
>in the temporal server shows me that the user is actually connected to
>it, although messages are delivered to it through is correct server. So
>I have had to manually kick that users in the temporal servers.
>> 
>> 	Is this the expected behaviour of the move command for director?
>> 
>> 	Is there any way to also force the kick of the imap/pop user's
>connection in the temporal server?
>
>Do you see any errors in logs? Especially:
>
>director: Error: connect(ipc) failed: Permission denied

Looks very familiar to me.

I'm having the same problem as Angel with director move that I have to kick the user logged into the proxy. Plus I'm also getting the ipc permission denied errors you mentioned.

Regards
Daniel




More information about the dovecot mailing list