doveadm-server protocol change?

[aki.tuomi at dovecot.fi]

> On May 30, 2016 at 9:54 PM Heiko Schlittermann <hs at schlittermann.de> wrote:
> 
> 
> 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

Hi!

You can get packages from http://xi.dovecot.fi/debian/,  if it helps. The HTTP API should not suffer from the username problem.

Aki