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 68A753938C1A for ; Wed, 6 May 2020 16:08:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 68A753938C1A Received: from [10.9.9.202] (helo=mailfront20.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1jWMaz-0001sm-9n for overseers@sourceware.org; Wed, 06 May 2020 18:08:29 +0200 Received: by mailfront20.runbox with esmtpsa [Authenticated alias (524175)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1jWMXb-0004au-GC for overseers@sourceware.org; Wed, 06 May 2020 18:04:59 +0200 Subject: Re: Stability of pipermail ml archive URLs To: overseers@sourceware.org References: <20200506141139.GJ2375@tucnak> <20200506152231.GA10446@cgf.cx> From: Per Bothner Message-ID: <8c414654-8458-ad50-9c34-3240a751ab26@bothner.com> Date: Wed, 6 May 2020 09:04:55 -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: <20200506152231.GA10446@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 16:08:41 -0000 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. Having each message containing a stable clean unique URL for that message is essential for any kind of web/email integration (by which I mean allowing people to comment/reply directly on the web-site). Ideally, the archive should be updated right after the message has been munged and when it is ready to go, but before the message is mailed to subscribers. However, if the archiver is less integrated with the mailer, it is acceptable for there to be a short delay while URL is "dangling". -- --Per Bothner per@bothner.com http://per.bothner.com/