From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cgf.cx (external.cgf.cx [107.170.62.102]) by sourceware.org (Postfix) with ESMTP id 693CC387090D for ; Thu, 7 May 2020 15:48:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 693CC387090D X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx 1EEB740B5B X-Spam-Level: X-Spam-CGF-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, TXREP autolearn=ham autolearn_force=no version=3.4.4 spammy=H*r:unknown, came, H*M:cgf, addition Received: by cgf.cx (sSMTP sendmail emulation); Thu, 07 May 2020 11:48:10 -0400 Date: Thu, 7 May 2020 11:48:10 -0400 From: Christopher Faylor To: gcc@gcc.gnu.org, overseers@sourceware.org Subject: Re: Stability of pipermail ml archive URLs Message-ID: <20200507154810.GA13473@cgf.cx> Mail-Followup-To: gcc@gcc.gnu.org, overseers@sourceware.org References: <20200506141139.GJ2375@tucnak> <20200506144446.GB2466959@elastic.org> <87r1vwxehp.fsf@euler.schwinge.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r1vwxehp.fsf@euler.schwinge.homeip.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, KHOP_HELO_FCRDNS, SPF_HELO_PASS, SPF_NEUTRAL, TXREP autolearn=no autolearn_force=no version=3.4.2 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 15:48:25 -0000 On Thu, May 07, 2020 at 11:48:18AM +0200, Thomas Schwinge wrote: >On 2020-05-06T10:44:46-0400, "Frank Ch. Eigler via Gcc" > wrote: >>>Can pipermail provide stable URLs at all? We really need those, we >>>reference those in commit messages, other mails, bugzilla etc. > >>It would be good to have another way of making permanent URLs for >>individual messages in mailing list archives. > >Look up by Message-ID? >, for >example. See , etc. The >idea is that for all practical purposes, Message-IDs are "sufficiently >unique". (Compare conceptually to the Git SHA-1 hashes.) IMO, we're making way too big a deal out of this. The message archives are changing because we are resequencing them. Mailman doesn't, AFAIK, take it upon itself to randomly renumber them. fche and cgf have been renumbering them when we remove spam. If we stopped doing that there would be no issue. When we were using ezmlm, I was careful not to remove message files when dealing with spam. We haven't been that careful with mailman and, so, we're seeing problems. If we just changed the way that we deal with spam to keep the message around but blank it out, we wouldn't have this problem. In addition, when I was migrating the mail archives from ezmlm to mailman I came across a number of cases where the same message-id was used in two messages. Possibly it was someone just bouncing email or maybe it was something else. Maybe it's a corner case but we wouldn't have to worry about this at all if we just used mailman's current numbering and didn't ever take it upon ourselves to rescan the archives. cgf