From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id UDntBkkl5mMzEwAAbAwnHQ (envelope-from ) for ; Fri, 10 Feb 2023 12:06:49 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id AC0NB0kl5mMbxwAA9RJhRA (envelope-from ) for ; Fri, 10 Feb 2023 12:06:49 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 01493A2EB for ; Fri, 10 Feb 2023 12:06:48 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pQREX-0001Cm-SX; Fri, 10 Feb 2023 06:06:25 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pQREW-0001Bw-8C for emacs-orgmode@gnu.org; Fri, 10 Feb 2023 06:06:24 -0500 Received: from relay-egress-host.us-east-2.a.mail.umich.edu ([13.59.128.245] helo=commutual-modron.relay-egress.a.mail.umich.edu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pQREU-0006hb-7H for emacs-orgmode@gnu.org; Fri, 10 Feb 2023 06:06:23 -0500 Received: from spruce-wendigo.authn-relay.a.mail.umich.edu (ip-10-0-74-62.us-east-2.compute.internal [10.0.74.62]) by commutual-modron.relay-egress.a.mail.umich.edu with ESMTPS id 63E62527.3A6A52D0.A32ACEE.123570; Fri, 10 Feb 2023 06:06:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=relay-2018-08-29; t=1676027175; bh=1y6rlZ2o4+l9TuFK1KWUUfdEALLgxRkIAzQ9V+LN+ps=; h=To:From:Subject:In-reply-to:References:Date; b=heRNLnWAD9EjGtQMbJF42/Q7aS5nSNIrlycZdL0jkebAyOgAokx5wDE0QHm/1waN2 15NgqKgaEUgBV1o8VAzDyJ/bZzv3ljleZ9l38qEHFuQjKkCzOznEAh79OAsN370TGx N2dsFZTmeqlNTyqf9M93sKGGv6szjes1jx1lG6bnSHf0KVU+/BIX5RdgJS+GywMGhH 0PqakcPjKjIrGI6y9gudCDnpNixHwB0mGGWvVJi0UbuEgSIXIwRoSPq24Ji/N2Ao+L a86NwTBcZLRecEcrfXJdQN6e48dBfDiXCeize30gZ75PMxBnVeZfu3fIbsBAqLibwh wcsqGlZ8v2joQ== Authentication-Results: spruce-wendigo.authn-relay.a.mail.umich.edu; iprev=fail policy.iprev=85.108.165.241 (Mismatch); auth=pass smtp.auth=minshall Received: from localhost (Mismatch [85.108.165.241]) by spruce-wendigo.authn-relay.a.mail.umich.edu with ESMTPSA id 63E62526.26803525.2FF30631.2263583; Fri, 10 Feb 2023 06:06:15 -0500 To: emacs-orgmode@gnu.org From: Greg Minshall Subject: Re: [BUG] list.orgmode.org managed to parse a message in future: 2023-10-29 [9.6.1 (release_9.6.1-223-gc8d20d @ /home/yantar92/.emacs.d/straight/build/org/)] In-reply-to: References: <87pmarnhlr.fsf@localhost> <2526494.1675622464@archlinux> Comments: In-reply-to Jean Louis message dated "Tue, 07 Feb 2023 21:57:27 +0300." X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 28.1.91 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2637626.1676027170.1@archlinux> Date: Fri, 10 Feb 2023 14:06:10 +0300 Message-ID: <2637627.1676027170@archlinux> Received-SPF: pass client-ip=13.59.128.245; envelope-from=minshall@umich.edu; helo=commutual-modron.relay-egress.a.mail.umich.edu X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-TUID: jAJtNK1IHHp4 Jean Louis, > In my opinion central computer that manages mailing lists should > recogniz if time of users is far in future and handle it > appropriately. > Maybe re-writing time with explanation in e-mail header would be more > appropriate. maybe something like that. though, this seems more an issue for "mailing list management" mailing lists than for org-mode itself. (maybe send them such a message, from the future? :) cheers, Greg