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.tu...@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]
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
