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 3132D383F842 for ; Thu, 7 May 2020 03:55:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3132D383F842 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx BD85A40481 X-Spam-Level: X-Spam-CGF-Status: No, score=-5.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, TXREP autolearn=ham autolearn_force=no version=3.4.4 spammy=H*r:unknown, H*M:cgf, Way, bet Received: by cgf.cx (sSMTP sendmail emulation); Wed, 06 May 2020 23:55:29 -0400 Date: Wed, 6 May 2020 23:55:29 -0400 From: Christopher Faylor To: Per Bothner Cc: overseers@sourceware.org Subject: Re: Stability of pipermail ml archive URLs Message-ID: <20200507035529.GB8900@cgf.cx> Mail-Followup-To: Per Bothner , overseers@sourceware.org References: <20200506141139.GJ2375@tucnak> <20200506152231.GA10446@cgf.cx> <8c414654-8458-ad50-9c34-3240a751ab26@bothner.com> <20200506205521.GA8900@cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-1262.4 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, JMQ_SPF_NEUTRAL, KAM_DMARC_NONE, KAM_DMARC_STATUS, KHOP_HELO_FCRDNS, SPF_HELO_PASS, SPF_NEUTRAL, TXREP, USER_IN_WHITELIST 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 03:55:37 -0000 On Wed, May 06, 2020 at 02:06:25PM -0700, Per Bothner wrote: >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. AFAICT, it's either a feature or a proposed feature in Mailman 3. Hard to believe it's 2020 and this isn't already a standard feature. cgf