Re: Broken Date formats

On Mon, 11 Mar 2024 16:17:20 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:

Michael S <already5chosen@yahoo.com> writes:

On Mon, 11 Mar 2024 17:18:18 +0200
Michael S <already5chosen@yahoo.com> wrote: 

 

xrn on linux is not confused (which is not surprising since
linux stores time internally as GMT anyway).
 
Date: 11 Mar 2024 11:10:15 +0000 (GMT)   

 
The issue does not appear to have anything to do with OS. It's all
about parsing of 'Date' header.
 
For example, in your message it looks like:
Date: Mon, 11 Mar 2024 14:50:03 GMT
Claws mail understand it.
 
In message of Tim Rentsch it looks like:
Date: Mon, 11 Mar 2024 07:54:07 -0700
Claws mail understand it.
 
In my messages format is the same as in Tim's.
 
In messages of Theo the header looks like a mix of yours and ours:
Date: 11 Mar 2024 11:10:15 +0000 (GMT)
 
The wonders of Postel's law.
 
 
 
 
 

>
Another formats that Claws Mail can't handle:
>
Date: Thu, 18 Jan 24 09:45:05 UTC
User-Agent: Pluto/3.18 (RISC OS/5.29) NewsHound/v1.52-32
>
Date: Fri, 06 Oct 23 15:40:16 +0000
User-Agent: Nemo/0.999a
>
Date: Sun, 04 Feb 24 12:39:24 GMT
User-Agent: Newsgrouper 0.3
>
In all cases the badness of the header (absence of year) is rather
obvious. IMHO, such obvious cases should be rejected by news servers,
but... Postel's Law :(
 

 
The RFC for the date line explicitly states that the
century is derived from the YY - use the closest
century (which is good until 2050).
 
So claws is not RFC compliant.

I didn't even pay attention that headers above contain year. Had fully
forgotten that YY format still exists.

If you're at it, how the reader is supposed to know that '18 Jan 24'
means 2024-01-18 and not 2018-01-24 ?