Re: Director & Master Users

Hello Sami, Thanks for the info. I have the following implemented and working. I am only using the Director nodes to map users to the same backend server. I perform all auth and message deliver/retrieval on the backend servers. Director Nodes: auth_master_user_separator = * passdb { driver =

Re: Director & Master Users

> On 15 Feb 2018, at 22.16, Travis Dolan wrote: > > It would look as though the changes have now negatively affected a "normal" > user from logging in. > > > telnet host 143 > > a login username password > > > a NO [AUTHENTICATIONFAILED] Authentication failed. >

Re: Director & Master Users

It would look as though the changes have now negatively affected a "normal" user from logging in. telnet host 143 a login username password a NO [AUTHENTICATIONFAILED] Authentication failed. telnet host 143 1 login devteam*masteru...@example.com password 1 OK [CAPABILITY IMAP4rev1 LITERAL+

Re: Director & Master Users

Awesome, thanks for the advice. Using the following now works... passdb { driver = static args = proxy=y password=doesnotmatter } Cheers. On Feb 15 2018, at 2:40 pm, Aki Tuomi wrote: > > On 15 February 2018 at 20:22 Travis Dolan wrote:

Re: Director & Master Users

> On 15 February 2018 at 20:22 Travis Dolan wrote: > > > Hello, > > I have Director setup to proxy requests to backend servers. This works fine > when using "standard" username/passwords. > > I am not try to enable the use of the Dovecot Master user through Director >

Director & Master Users

Hello, I have Director setup to proxy requests to backend servers. This works fine when using "standard" username/passwords. I am not try to enable the use of the Dovecot Master user through Director into the backend servers. a.) username is being sent as masteruser*username b.) request hits