On Wed, May 28, 2025 at 12:53 PM Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
On 28/05/2025 12:33 EEST Brent Clark via dovecot <dovecot@dovecot.org> wrote:
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 usinga 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 adifferent 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!
Please see https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html and https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar...., hopefully these already help you forward.
Aki
You guys need to fix that example config archive!
root@eu:/home/wash/Mara.Cloud# wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... --2025-05-28 13:03:53-- https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... Resolving github.com (github.com)... 140.82.121.3 Connecting to github.com (github.com)|140.82.121.3|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘dovecot-2.4.0-example-config.tar.gz’
dovecot-2.4.0-example-config.tar.gz [ <=>
] 172.85K --.-KB/s in0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
root@eu:/home/wash/Mara.Cloud# tar -zxvf dovecot-2.4.0-example-config.tar.gz
gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On Wed, May 28, 2025 at 12:53 PM Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
> On 28/05/2025 12:33 EEST Brent Clark via dovecot
<dovecot@dovecot.org> wrote:
>
>
> 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
Hi!
Please see https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-
2.4.html and https://github.com/dovecot/tools/blob/main/dovecot-
2.4.0-example-config.tar.gz, hopefully these already help you
forward.
AkiYou guys need to fix that example config archive!
root@eu:/home/wash/Mara.Cloud# wget https://github.com/dovecot/tools/blob/main/ dovecot-2.4.0-example-config.tar.gz --2025-05-28 13:03:53-- https://github.com/dovecot/tools/blob/main/dovecot- 2.4.0-example-config.tar.gz Resolving github.com (github.com)... 140.82.121.3 Connecting to github.com (github.com)|140.82.121.3|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘dovecot-2.4.0-example-config.tar.gz’
dovecot-2.4.0-example-config.tar.gz [ <=> ] 172.85K --.-KB/s in 0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
root@eu:/home/wash/Mara.Cloud# tar -zxvf dovecot-2.4.0-example-config.tar.gz
gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html]