Help Translating Dovecot 2.3 Proxy Configuration to 2.4

Hi all,

I'm in the process of upgrading from Dovecot 2.3 to 2.4 and would appreciate some help translating an existing configuration that uses a proxy lookup for user and password databases.

Here's the relevant 2.3 configuration:

|passdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } userdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } uri= proxy:/var/run/mail_directory_service/socket:somewhere password_key= passdb/%u user_key= userdb/%u iterate_disable= yes |

This configuration was working fine in 2.3 to proxy user and password lookups to an external service via a Unix socket. However, Dovecot 2.4 has reworked configuration parsing, and this syntax no longer appears valid. I couldn’t find a direct equivalent in the 2.4 documentation.

Could someone advise how this should be adapted for 2.4?

    What’s the correct way to specify the proxy: URI in 2.4?

    Are password_key and user_key still supported, or should I be using a different mechanism?

    Is iterate_disable = yes still relevant or required in this context?

Any guidance, examples, or pointers to migration resources would be very helpful.

Thanks in advance, Brent Clark

Hi all, I'm in the process of upgrading from Dovecot 2.3 to 2.4 and would appreciate some help translating an existing configuration that uses a proxy lookup for user and password databases. Here's the relevant 2.3 configuration: passdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } userdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext }

uri = proxy:/var/run/mail_directory_service/socket:somewhere password_key = passdb/%u user_key = userdb/%u iterate_disable = yes

This configuration was working fine in 2.3 to proxy user and password lookups to an external service via a Unix socket. However, Dovecot 2.4 has reworked configuration parsing, and this syntax no longer appears valid. I couldn’t find a direct equivalent in the 2.4 documentation.

Could someone advise how this should be adapted for 2.4?

    What’s the correct way to specify the proxy: URI in 2.4?

    Are password_key and user_key still supported, or should I be using a different mechanism?

    Is iterate_disable = yes still relevant or required in this context?

Any guidance, examples, or pointers to migration resources would be very helpful.

Thanks in advance, Brent Clark