From: Jean Louis <bugs@gnu.support>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Bastien Guerry <bzg@fsf.org>
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/)]
Date: Fri, 3 Feb 2023 14:38:50 +0300 [thread overview]
Message-ID: <Y9zySvjbaxen0nUH@protected.localdomain> (raw)
In-Reply-To: <87pmarnhlr.fsf@localhost>
* Ihor Radchenko <yantar92@posteo.net> [2023-02-03 14:13]:
> Hi,
>
> We currently have a message in future on top of
> https://list.orgmode.org/
>
> 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.
>
> Are we observing public inbox bug?
Sorry for that. It was not intentional. It happened during the
exercises.
I went to future, and wrote from there. ☺️
Now it is pending until the future time stamp.
Similarly, I have made mess with Dino XMPP messenger as well, I have
sent message from future, now that message will appear to me for years
as the last message sent, no matter what I do, that message remains
pending!
Why did mailing list accept message from far future? It should not be
so, that is bug to be reported.
Dino messenger accepted message from far future, that is bug, and I
have reported it:
https://github.com/dino/dino/issues/1355
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-03 11:50 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 [this message]
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 ` future value for Date header can pin thread to top of $inbox/ " Kyle Meyer
2023-02-04 17:37 ` [BUG] " 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=Y9zySvjbaxen0nUH@protected.localdomain \
--to=bugs@gnu.support \
--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).