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
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...., hopefully these already help you forward.
Aki
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]
On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot <dovecot@dovecot.org> wrote:
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]
The tar is fine, your wget is not.
Aki
Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=>
] 173.07K 179KB/s in1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
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 beusing a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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 beusing a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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/sin 0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
The tar is fine, your wget is not.
Aki
-- 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]
Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0- example-config.tar.gz --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot- 2.4.0-example-config.tar.gz Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=> ] 173.07K 179KB/s in 1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
> On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot
<dovecot@dovecot.org> wrote:
>
>
> 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.
> >
> > 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.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]
>
The tar is fine, your wget is not.
Aki-- 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]
Hi.
On Wed, 28 May 2025 22:44:19 +0300 Odhiambo Washington via dovecot <dovecot@dovecot.org> wrote:
Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar....
Sorry to say that but I get a html page return with the curl call. curl -LOv https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar....
A cross check with the browser shows a github page.
This commandline works for me.
curl -vLO https://raw.githubusercontent.com/dovecot/tools/66aa639e132b9c0c459d23705ae0...
Regards alex
--2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=>
] 173.07K 179KB/sin 1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
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 shouldI be using a different mechanism?
Is iterate_disable = yes still relevant or required inthis 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 shouldI be using a different mechanism?
Is iterate_disable = yes still relevant or required inthis 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 in 0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
The tar is fine, your wget is not.
Aki
On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot <dovecot@dovecot.org> wrote:
Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.... Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=>
] 173.07K 179KB/s in1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
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 beusing a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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 beusing a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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/sin 0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
The tar is fine, your wget is not.
Aki
-- 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] Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0- example-config.tar.gz --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot- 2.4.0-example-config.tar.gz Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=> ] 173.07K 179KB/s in 1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
> On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot <dovecot@dovecot.org> wrote: > > > 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. > > > > 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.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] > The tar is fine, your wget is not. Aki
If you open the link first and then pick up the link to download it as raw file, it'll actually work.
Aki
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file. I have had to follow a convoluted process to open it, when a tar -xzf should be enough.
On Wed, May 28, 2025 at 11:04 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar....
--2025-05-28 22:41:01--
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar....
Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=>
] 173.07K 179KB/sin 1.0s
2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz' saved [177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
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 Ibe using a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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 beusing a different mechanism?
Is iterate_disable = yes still relevant or required in thiscontext?
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/sin 0.07s
2025-05-28 13:03:54 (2.57 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [176999]
The tar is fine, your wget is not.
Aki
-- 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] Well, the wget was the native one from Debian 12 (Bookworm).
Now:
wash@gw:~$ uname -a FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-2.4.0- example-config.tar.gz --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/main/dovecot- 2.4.0-example-config.tar.gz Resolving github.com (github.com)... 140.82.113.3 Connecting to github.com (github.com)|140.82.113.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 [ <=>
] 173.07K 179KB/s in 1.0s2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-config.tar.gz'
saved
[177227]
wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz tar: Error opening archive: Unrecognized archive format wash@gw:~$
I have previously downloaded that archive and had to go through hoops to get the files, even on Windows using 7zip!
I hope I am not crazy, or all my computers haven't adopted my craziness!
On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
> On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot <dovecot@dovecot.org> wrote: > > > 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 configurationthat 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. > > > > 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.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] >
The tar is fine, your wget is not. AkiIf you open the link first and then pick up the link to download it as raw file, it'll actually work.
Aki
-- 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]
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file. I have had to follow a convoluted process to open it, when a tar -xzf should be enough.
On Wed, May 28, 2025 at 11:04 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
> On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot
<dovecot@dovecot.org> wrote:
>
>
> Well, the wget was the native one from Debian 12 (Bookworm).
>
> Now:
>
> wash@gw:~$ uname -a
> FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1
GENERIC
> amd64
> wash@gw:~$ wget
> https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-
config.tar.gz
> --2025-05-28 22:41:01--
> https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-
config.tar.gz
> Resolving github.com (github.com)... 140.82.113.3
> Connecting to github.com (github.com)|140.82.113.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 [
<=>
>
> ] 173.07K
179KB/s in
> 1.0s
>
> 2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-
config.tar.gz'
> saved [177227]
>
> wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz
> tar: Error opening archive: Unrecognized archive format
> wash@gw:~$
>
> I have previously downloaded that archive and had to go through
hoops to
> get the files, even on Windows using 7zip!
>
> I hope I am not crazy, or all my computers haven't adopted my
craziness!
>
>
> On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-
xchange.com>
> wrote:
>
> >
> > > On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot <
> > dovecot@dovecot.org> wrote:
> > >
> > >
> > > 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.
> > > >
> > > > 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.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]
> > >
> >
> > The tar is fine, your wget is not.
> >
> > Aki
> >
> >
>
> --
> 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]
> Well, the wget was the native one from Debian 12 (Bookworm).
>
> Now:
>
> wash@gw:~$ uname -a
> FreeBSD gw.kictanet.or.ke 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1
GENERIC amd64
> wash@gw:~$ wget https://github.com/dovecot/tools/blob/main/dovecot-
2.4.0-
> example-config.tar.gz
> --2025-05-28 22:41:01-- https://github.com/dovecot/tools/blob/
main/dovecot-
> 2.4.0-example-config.tar.gz
> Resolving github.com (github.com)... 140.82.113.3
> Connecting to github.com (github.com)|140.82.113.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 [
<=>
>
> ] 173.07K 179KB/s in
1.0s
>
> 2025-05-28 22:41:04 (179 KB/s) - 'dovecot-2.4.0-example-
config.tar.gz' saved
> [177227]
>
> wash@gw:~$ tar xzvf dovecot-2.4.0-example-config.tar.gz
> tar: Error opening archive: Unrecognized archive format
> wash@gw:~$
>
> I have previously downloaded that archive and had to go through
hoops to get
> the files, even on Windows using 7zip!
>
> I hope I am not crazy, or all my computers haven't adopted my
craziness!
>
>
> On Wed, May 28, 2025 at 10:36 PM Aki Tuomi <aki.tuomi@open-
xchange.com> wrote:
>
> > On 28/05/2025 22:30 EEST Odhiambo Washington via dovecot
> <dovecot@dovecot.org> wrote:
> >
> >
> > 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.
> > >
> > > 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.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]
> >
>
> The tar is fine, your wget is not.
>
> Aki
>
>
If you open the link first and then pick up the link to download it
as raw file, it'll actually work.
Aki-- 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]
It was a link to the file location in the git repo, not a download
link. The file is fine.
Quoting Odhiambo Washington via dovecot <dovecot@dovecot.org>:
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file. I have had to follow a convoluted process to open it, when a tar -xzf should be enough.
On Wed, May 28, 2025 at 11:04 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
> > 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. > > > > 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.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] >
The tar is fine, your wget is not. AkiIf you open the link first and then pick up the link to download it as raw file, it'll actually work.
Aki
-- 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]
Aha!
Is my tar the issue, on all OSes? Debian, Ubuntu, FreeBSD? I don't think so.
How do you extract that file in Linux? tar -zxf FILENAME.tar.gz??
On Fri, May 30, 2025 at 8:41 PM Patrick Domack via dovecot < dovecot@dovecot.org> wrote:
It was a link to the file location in the git repo, not a download link. The file is fine.
Quoting Odhiambo Washington via dovecot <dovecot@dovecot.org>:
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file. I have had to follow a convoluted process to open it, when a tar -xzf should be enough.
On Wed, May 28, 2025 at 11:04 PM Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
> > 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. > > > > 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.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] > The tar is fine, your wget is not. AkiIf you open the link first and then pick up the link to download it as raw file, it'll actually work.
Aki
-- 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]
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
-- 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]
Aha!
Is my tar the issue, on all OSes? Debian, Ubuntu, FreeBSD? I don't think so.
How do you extract that file in Linux? tar -zxf FILENAME.tar.gz??
On Fri, May 30, 2025 at 8:41 PM Patrick Domack via dovecot <dovecot@dovecot.org> wrote: It was a link to the file location in the git repo, not a download link. The file is fine.
Quoting Odhiambo Washington via dovecot <dovecot@dovecot.org>:
> There is no reason why anyone should go through a 'special download
> process' to open a .tar.gz, or no?
> I suppose you just need to fix whatever is wrong with the file.
> I have had to follow a convoluted process to open it, when a tar -
xzf
> should be enough.
>
> On Wed, May 28, 2025 at 11:04 PM Aki Tuomi <aki.tuomi@open-
xchange.com>
> wrote:
>
>>
>> > On 28/05/2025 22:44 EEST Odhiambo Washington via dovecot <
>> dovecot@dovecot.org> wrote:
>> >
>> >
>> > > > 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.
>> > > >
>> > > > 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.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]
>> > >
>> >
>> > The tar is fine, your wget is not.
>> >
>> > Aki
>> >
>> >
>>
>> If you open the link first and then pick up the link to download
it as raw
>> file, it'll actually work.
>>
>> Aki
>>
>>
>
> --
> 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]
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-leave@dovecot.org-- 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, 28 May 2025, Odhiambo Washington wrote:
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file.
This issue bites me often. There's nothing wrong with the archive -- the original URL you used
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.gzis not interpreted by Github as an archive file, but a page describing the content. If you use a browser to extract the raw download link
https://github.com/dovecot/tools/raw/refs/heads/main/dovecot-2.4.0-example-config.tar.gzwget can work with that. It worked for me, at least.
Joseph Tam <jtam.home@gmail.com>
On Sat, May 31, 2025 at 12:45 AM Joseph Tam via dovecot <dovecot@dovecot.org> wrote:
On Wed, 28 May 2025, Odhiambo Washington wrote:
There is no reason why anyone should go through a 'special download process' to open a .tar.gz, or no? I suppose you just need to fix whatever is wrong with the file.
This issue bites me often. There's nothing wrong with the archive -- the original URL you used
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar....
is not interpreted by Github as an archive file, but a page describing the content. If you use a browser to extract the raw download link
https://github.com/dovecot/tools/raw/refs/heads/main/dovecot-2.4.0-example-c...
wget can work with that. It worked for me, at least.
I fetched that with wget, and it extracted the way I'd expect! The thing has bothered me for weeks now! Thanks.
[cut]
Saving to: ‘dovecot-2.4.0-example-config.tar.gz’
dovecot-2.4.0-example-config.tar.gz
100%[========================================================================================================================================>]
28.25K --.-KB/s in 0.003s
2025-05-31 00:49:17 (7.90 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’
saved [28930/28930]
wash@eu:~/Mara$ tar -zxvf dovecot-2.4.0-example-config.tar.gz
conf.d/
conf.d/auth-system.conf.ext
conf.d/99-local.conf
conf.d/20-submission.conf
conf.d/20-lmtp.conf
conf.d/auth-sql.conf.ext
conf.d/auth-master.conf.ext
conf.d/15-lda.conf
conf.d/20-managesieve.conf
conf.d/10-ssl.conf
conf.d/30-dict-server.conf
conf.d/auth-static.conf.ext
conf.d/90-sieve.conf
conf.d/auth-oauth2.conf.ext
conf.d/15-mailboxes.conf
conf.d/20-pop3.conf
conf.d/10-mail.conf
conf.d/auth-ldap.conf.ext
conf.d/90-acl.conf
conf.d/auth-passwdfile.conf.ext
conf.d/10-logging.conf
conf.d/10-master.conf
conf.d/10-metrics.conf
conf.d/20-imap.conf
conf.d/auth-deny.conf.ext
conf.d/10-auth.conf
conf.d/90-quota.conf
conf.d/90-fts.conf
dovecot.conf
local.conf
README
--
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 Sat, May 31, 2025 at 12:45 AM Joseph Tam via dovecot <dovecot@dovecot.org>
wrote:
On Wed, 28 May 2025, Odhiambo Washington wrote:
> There is no reason why anyone should go through a 'special download
> process' to open a .tar.gz, or no?
> I suppose you just need to fix whatever is wrong with the file.
This issue bites me often. There's nothing wrong with the archive --
the original URL you used
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-
example-config.tar.gz
is not interpreted by Github as an archive file, but a page
describing
the content. If you use a browser to extract the raw download link
https://github.com/dovecot/tools/raw/refs/heads/main/dovecot-
2.4.0-example-config.tar.gz
wget can work with that. It worked for me, at least.
I fetched that with wget, and it extracted the way I'd expect!
The thing has bothered me for weeks now! Thanks.
[cut] Saving to: ‘dovecot-2.4.0-example-config.tar.gz’
dovecot-2.4.0-example-config.tar.gz 100% [========================================================================================================================================>] 28.25K --.-KB/s in 0.003s
2025-05-31 00:49:17 (7.90 MB/s) - ‘dovecot-2.4.0-example-config.tar.gz’ saved [28930/28930]
wash@eu:~/Mara$ tar -zxvf dovecot-2.4.0-example-config.tar.gz conf.d/ conf.d/auth-system.conf.ext conf.d/99-local.conf conf.d/20-submission.conf conf.d/20-lmtp.conf conf.d/auth-sql.conf.ext conf.d/auth-master.conf.ext conf.d/15-lda.conf conf.d/20-managesieve.conf conf.d/10-ssl.conf conf.d/30-dict-server.conf conf.d/auth-static.conf.ext conf.d/90-sieve.conf conf.d/auth-oauth2.conf.ext conf.d/15-mailboxes.conf conf.d/20-pop3.conf conf.d/10-mail.conf conf.d/auth-ldap.conf.ext conf.d/90-acl.conf conf.d/auth-passwdfile.conf.ext conf.d/10-logging.conf conf.d/10-master.conf conf.d/10-metrics.conf conf.d/20-imap.conf conf.d/auth-deny.conf.ext conf.d/10-auth.conf conf.d/90-quota.conf conf.d/90-fts.conf dovecot.conf local.conf README
-- 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]
participants (6)
-
Aki Tuomi
-
alex
-
Brent Clark
-
Joseph Tam
-
Odhiambo Washington
-
Patrick Domack