From: Per Bothner <per@bothner.com>
To: overseers@sourceware.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Wed, 6 May 2020 09:04:55 -0700 [thread overview]
Message-ID: <8c414654-8458-ad50-9c34-3240a751ab26@bothner.com> (raw)
In-Reply-To: <20200506152231.GA10446@cgf.cx>
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.
Having each message containing a stable clean unique URL for that message
is essential for any kind of web/email integration (by which I mean allowing
people to comment/reply directly on the web-site).
Ideally, the archive should be updated right after the message has been
munged and when it is ready to go, but before the message is mailed to subscribers.
However, if the archiver is less integrated with the mailer, it is acceptable for
there to be a short delay while URL is "dangling".
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2020-05-06 16:08 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 [this message]
2020-05-06 20:55 ` Christopher Faylor
2020-05-06 21:06 ` Per Bothner
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=8c414654-8458-ad50-9c34-3240a751ab26@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).