From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: downloading list archive mboxes |
Date: | 2022-06-25 19:01:07 |
Message-ID: | CABUevExKMrTWvgOfrPCdyfqyiEVzySvSq2pMtuNZ8HK6Wgfz7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Sat, Jun 25, 2022 at 8:47 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Sat, Jun 25, 2022 at 11:40 AM Justin Pryzby <pryzby(at)telsasoft(dot)com>
> wrote:
>
>> I used to be able to wget the "download mbox" link.
>> https://www.postgresql.org/list/pgsql-hackers/
>>
>> I hope that can be fixed, unless it was deliberate, which would be
>> unfortunate.
>>
>>
> It was intentional.
>
>
> https://www.postgresql.org/message-id/CABUevEwdNvNUFBDeMJSJ0sMDapKDgESwoYPmH%2BMN3FkTVJ%2BRVw%40mail.gmail.com
>
>
It was indeed deliberate. Are there any locations where it still *tells*
you to use the archives/antispam method?
FWIW, the old method should still work fine as long as you provide the
username/password in basic auth up front. Can you explain exactly the
scenario in which it fails? Like, what command did you actually use?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-06-25 19:12:13 | Re: downloading list archive mboxes |
Previous Message | David G. Johnston | 2022-06-25 18:46:53 | Re: downloading list archive mboxes |