doveadm-server protocol change?

[Heiko Schlittermann]

Hi Aki,

thank your for responding that fast.

aki.tuomi at dovecot.fi <aki.tuomi at dovecot.fi> (Mo 30 Mai 2016 17:49:53 CEST):
…
> Hi! This has been fixed in 2.2.24. There was a bug in user passing. 

Ok, thus at least your answer saves me hours of debugging. We upgraded
old Ubuntu Boxes (14.04/LTS) to 16.04 to get around some Dovecot
limitations/problems. And now we got new ones :(

We did the upgrade to avoid self-built binaries and use the distro
packages. Probably we're out of luck.

> We also invite you to have a go at our HTTP based interface, see http://wiki.dovecot.org/Design/DoveadmProtocol/HTTP   

Does the 2.2.22 HTTP API suffer from the same bug with user passing?
Is the HTTP API useable in a Director/Backend configuration?

Our setup is about

    [ mx ] ---> dovecot-protocol ---> [ director ] ----> [ backend ]
                                                   `---> [ backend ]
                                                     `-> [ backend ]

The bug w/ user passing is in the backend? Or already in the directors?
-- 
Heiko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://dovecot.org/pipermail/dovecot/attachments/20160530/6f7d834d/attachment.sig>