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]