public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: overseers@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Thu, 7 May 2020 13:56:04 -0400	[thread overview]
Message-ID: <20200507175604.GC3563678@elastic.org> (raw)
In-Reply-To: <20200507155442.GB13473@cgf.cx>

Hi -

> >I was thinking we might be able to trick pipermail (the web archiver
> >component) to simply name the message web urls after some function of
> >the message-id instead of the sequence number.  Will give this a try
> >very shortly.
> 
> I just want to go on record as saying that I think this is a bad idea.
> We can fix this problem simply without redesigning pipermail.

If the idea requires more than a dozenish lines of code, then I agree
it's not worth doing.  "redesigning" - indeed no thanks.


> The problem that we're seeing is caused by a script that I wrote to
> migrate ezmlm to mailman.  The fix for the problem is "Don't run
> that script".

Yeah, but that is the official mailman2 method for this.  Spam/malware
that gets through can sit in multiple locations unless we clean it out
in the proper thorough manner, through the entire pipeline (which
starts with the mbox files).  Not super keen on building much
complexity that operates on all the intermediate results and html
files.


- FChE

  reply	other threads:[~2020-05-07 17:56 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 [this message]
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
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=20200507175604.GC3563678@elastic.org \
    --to=fche@elastic.org \
    --cc=gcc@gcc.gnu.org \
    --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).