emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Bastien Guerry <bzg@fsf.org>
Subject: future value for Date header can pin thread to top of $inbox/ 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/)]
Date: Sat, 04 Feb 2023 12:32:00 -0500	[thread overview]
Message-ID: <87cz6pgwvj.fsf@kyleam.com> (raw)
In-Reply-To: <87pmarnhlr.fsf@localhost>

Ihor Radchenko writes:

> We currently have a message in future on top of
> https://list.orgmode.org/

Hmm, that's unfortunate.

> The message is
> https://list.orgmode.org/ZT2vNKsf3Lp5xit3@protected.localdomain/raw, and
> it does not contain the future dates in headers. Just in the body.

Look again at its date header:

  $ curl -fSsL https://list.orgmode.org/ZT2vNKsf3Lp5xit3@protected.localdomain/raw | \
    grep Date:
  Date: Sun, 29 Oct 2023 04:02:44 +0300

> Are we observing public inbox bug?

I'm not sure what's intended here.  There are spots in public-inbox that
favor a date from Received headers.  I've sent a message to
public-inbox's list:

  https://public-inbox.org/meta/87edr5gx63.fsf@kyleam.com


  parent reply	other threads:[~2023-02-04 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 10:55 [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/)] Ihor Radchenko
2023-02-03 11:38 ` Jean Louis
2023-02-05 18:41   ` Greg Minshall
2023-02-07 18:57     ` Jean Louis
2023-02-10 11:06       ` Greg Minshall
2023-02-04 16:02 ` Max Nikulin
2023-02-04 17:32 ` Kyle Meyer [this message]
2023-02-04 17:37   ` Kyle Meyer
2023-02-04 21:42   ` Kyle Meyer
2023-02-05 15:11     ` Ihor Radchenko
2023-02-06 10:12       ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cz6pgwvj.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=bzg@fsf.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).