public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: overseers@sourceware.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Wed, 6 May 2020 14:06:25 -0700	[thread overview]
Message-ID: <c3754a35-889b-6ffe-d5a2-12d53b595216@bothner.com> (raw)
In-Reply-To: <20200506205521.GA8900@cgf.cx>

On 5/6/20 1:55 PM, Christopher Faylor wrote:
> On Wed, May 06, 2020 at 09:04:55AM -0700, Per Bothner wrote:
>> On 5/6/20 8:22 AM, Christopher Faylor via Overseers wrote:
>>> I'll bet this is due to rebuilding the archive after removing spam.
>>>
>>> Maybe we need to revisit how that's done.
>>
>> The Correct Way to Handle This is for each message to contain an
>> Archived-At header (https://tools.ietf.org/html/rfc5064) generated by Mailman.
>> Pipermail should use that header when building the archive.
> 
> AFAIK, mailman doesn't support this out of the box.

That is my impression, too - and I'm astounded it still hasn't been fixed.
It's a major missing feature, IMO.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2020-05-06 21:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:11 Jakub Jelinek
2020-05-06 14:44 ` Frank Ch. Eigler
2020-05-06 14:54   ` Arseny Solokha
2020-05-06 15:24     ` Christopher Faylor
2020-05-06 14:55   ` Arseny Solokha
2020-05-07  9:48   ` Thomas Schwinge
2020-05-07 10:14     ` Frank Ch. Eigler
2020-05-07 15:54       ` Christopher Faylor
2020-05-07 17:56         ` Frank Ch. Eigler
2020-05-07 18:27           ` Christopher Faylor
2020-05-07 15:48     ` Christopher Faylor
2020-05-07 19:23     ` Segher Boessenkool
2020-05-07 20:28       ` Christopher Faylor
2020-05-06 15:22 ` Christopher Faylor
2020-05-06 16:04   ` Per Bothner
2020-05-06 20:55     ` Christopher Faylor
2020-05-06 21:06       ` Per Bothner [this message]
2020-05-07  3:55         ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3754a35-889b-6ffe-d5a2-12d53b595216@bothner.com \
    --to=per@bothner.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).