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/)]

2023-02-10 Thread Greg Minshall
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

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/)]

2023-02-07 Thread Jean Louis
* Greg Minshall [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

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/)]

2023-02-06 Thread Ihor Radchenko
Ihor Radchenko writes: > Kyle Meyer writes: > >> Eric replied with a patch that resolved the issue. I've installed it. > > Thanks! > I think I saw the "future" thread disappearing briefly, but it is again > there on top of https://list.orgmode.org/. I no longer see the problem and, as per

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/)]

2023-02-05 Thread Greg Minshall
Jean Louis, > Why did mailing list accept message from far future? It should not be > so, that is bug to be reported. there's an old internet adage to help achieve interoperability (attributed to the late Jon Postel): be liberal in what you accept, and conservative in what you send. so, i

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/)]

2023-02-05 Thread Ihor Radchenko
Kyle Meyer writes: > Eric replied with a patch that resolved the issue. I've installed it. Thanks! I think I saw the "future" thread disappearing briefly, but it is again there on top of https://list.orgmode.org/. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode

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/)]

2023-02-04 Thread Kyle Meyer
Kyle Meyer writes: > 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@kyleam.com Eric replied with a patch that resolved the issue.

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/)]

2023-02-04 Thread Kyle Meyer
Oy, sorry about mangling the subject :x I started to change it to cc but then decided to start send a separate message, but forgot about the in-between subject change.

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/)]

2023-02-04 Thread Max Nikulin
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

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/)]

2023-02-03 Thread Jean Louis
* Ihor Radchenko [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

[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/)]

2023-02-03 Thread Ihor Radchenko
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? -- Ihor Radchenko //