From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) by sourceware.org (Postfix) with ESMTPS id 73EAB388F076 for ; Wed, 6 May 2020 21:06:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 73EAB388F076 Received: from [10.9.9.204] (helo=mailfront22.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1jWRFe-0005Pe-9w for overseers@sourceware.org; Wed, 06 May 2020 23:06:47 +0200 Received: by mailfront22.runbox with esmtpsa [Authenticated alias (524175)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1jWRFN-0005po-A3 for overseers@sourceware.org; Wed, 06 May 2020 23:06:29 +0200 Subject: Re: Stability of pipermail ml archive URLs To: overseers@sourceware.org References: <20200506141139.GJ2375@tucnak> <20200506152231.GA10446@cgf.cx> <8c414654-8458-ad50-9c34-3240a751ab26@bothner.com> <20200506205521.GA8900@cgf.cx> From: Per Bothner Message-ID: Date: Wed, 6 May 2020 14:06:25 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200506205521.GA8900@cgf.cx> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS 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: Wed, 06 May 2020 21:06:53 -0000 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. -- --Per Bothner per@bothner.com http://per.bothner.com/