From: Jean Louis <bugs@gnu.support>
To: Ihor Radchenko <yantar92@posteo.net>,
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: Tue, 7 Feb 2023 21:57:27 +0300 [thread overview]
Message-ID: <Y+KfF9xueQZ7p7+S@protected.localdomain> (raw)
In-Reply-To: <2526494.1675622464@archlinux>
* Greg Minshall <minshall@umich.edu> [2023-02-05 21:43]:
> so, i wouldn't blame mail services for accepting mail with odd dates.
> but, i would question MUAs (like mh-e, mutt, etc., i guess) that allow
> one to send e-mail with odd dates. (i mean, i guess if the person
> stands on their head and swears up and down that they mean to do it,
`mutt' is program that receives date from system date. Nothing wrong
with it alone.
You cannot blame computer program for doing what is
instructed. Programs know the time we gave to them.
A server for mailing list is much more important program than single
MUA.
Mailing list solves communication of many people.
Such computer is always online and can easily synchronize time with
Internet servers.
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.
--
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-07 21: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 [this message]
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=Y+KfF9xueQZ7p7+S@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).