From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f]) by sourceware.org (Postfix) with ESMTPS id 76625396DC20 for ; Thu, 7 May 2020 17:56:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 76625396DC20 Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jWkkf-0000qG-5B; Thu, 07 May 2020 17:56:05 +0000 Received: from very.elastic.org ([192.168.1.1]) by elastic.org with esmtp (Exim 4.92.3) (envelope-from ) id 1jWkke-000OH8-PX; Thu, 07 May 2020 13:56:04 -0400 Received: from fche by very.elastic.org with local (Exim 4.92.3) (envelope-from ) id 1jWkke-00FDLA-Ov; Thu, 07 May 2020 13:56:04 -0400 Date: Thu, 7 May 2020 13:56:04 -0400 From: "Frank Ch. Eigler" To: overseers@sourceware.org, gcc@gcc.gnu.org Subject: Re: Stability of pipermail ml archive URLs Message-ID: <20200507175604.GC3563678@elastic.org> References: <20200506141139.GJ2375@tucnak> <20200506144446.GB2466959@elastic.org> <87r1vwxehp.fsf@euler.schwinge.homeip.net> <20200507101455.GC2466959@elastic.org> <20200507155442.GB13473@cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200507155442.GB13473@cgf.cx> X-Sender-Verification: "" X-Sender-Verification: "" X-Spam-Status: No, score=-105.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP, USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2020 17:56:07 -0000 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