From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.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: Sat, 4 Feb 2023 23:02:16 +0700 [thread overview]
Message-ID: <trlvia$tge$1@ciao.gmane.io> (raw)
In-Reply-To: <87pmarnhlr.fsf@localhost>
On 03/02/2023 17:55, Ihor Radchenko wrote:
>
> We currently have a message in future on top of
> https://list.orgmode.org/
At the epoch of livejournal some users intentionally assign some date in
the the future to pin posts at the top of their blogs.
> 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.
See the "Date" header
> Date: Sun, 29 Oct 2023 04:02:44 +0300
> Are we observing public inbox bug?
Earlier I have seen spam messages from the future. I think, it just was
easier to take time from the Date header. Parsing of "Received" headers
is more complicated and it is necessary to configure which one can be
trusted. Sender may add some fake "Received" headers as well. Moreover
it is necessary to ensure that time is correct on the trusted server.
(It must be done anyway, incorrect time may lead to failure of TLS
handshake before message transfer.)
I am not convinced that mail list must drop messages with future date.
Public inbox may have some feature like override map Message-ID ->
correct date or parsing "Received" headers. The latter may increase
server load during mail processing.
next prev parent reply other threads:[~2023-02-04 16:03 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 [this message]
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='trlvia$tge$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).