From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from out-215.mta1.migadu.com (out-215.mta1.migadu.com [IPv6:2001:41d0:203:375::d7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id C86E21F5A0 for ; Sat, 4 Feb 2023 17:26:01 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=kyleam.com header.i=@kyleam.com header.a=rsa-sha256 header.s=key1 header.b=YoCPSCxA; dkim-atps=neutral X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1675531555; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=+T/uOL8neyX9esbM91EDEO3c75x14tPQbGD+eg/irWw=; b=YoCPSCxANUZd/SmW0EUx7f6UOUwApSJWQXIiS+mUxE/oCq+4K7yhWr6DBX0edTEP/SA/ug 8UltUdjT33GaTDnwlon60hpCwphbJxcUo6adJuQckJAor0QRyx9q5OOU/18eDvHAzKvFc/ 5YJPvIhhNlLqyZ7ITubdpLdwV0yFZ8x1ocK04vk2J190f7pShbTHIE6F5EkaOH3G0nx+j5 kEWeXBUkIABiHvZq7Un4eLiYCFqYd54IPRubwWPgndghsYRGV5DzFoeaqLHJIOWIYML145 Su3dO5t98c2gXgCG72ndTMRLK/4rU1DOYdGFa1kMA0Oz0L/gaLmu8LvEKYhTkg== From: Kyle Meyer To: Eric Wong , meta@public-inbox.org Cc: Ihor Radchenko , Bastien Guerry Subject: future date in Date header pinning thread to top of $inbox/ Date: Sat, 04 Feb 2023 12:25:40 -0500 Message-ID: <87edr5gx63.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT List-Id: As noted by Ihor on the Org list (<87pmarnhlr.fsf@localhost>), Org's public-inbox archive has a thread pinned to the top of the $inbox/ overview: * https://yhetil.org/orgmode/ That thread has a message where a sender set his Date to a future date: $ curl -fSsL https://yhetil.org/orgmode/ZT2vNKsf3Lp5xit3@protected.localdomain/raw | \ grep Date: Date: Sun, 29 Oct 2023 04:02:44 +0300 Based on grepping around the public-inbox tree and Git history, I know that there are spots in public-inbox that prefer a date from the Received headers over the one from the Date header. Would that make sense to do here too to reduce the chances of a date from the future pinning a thread? (Or perhaps that's already the intention and something's off here?) Thanks.