Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.arch
Subject: Re: Broken Date formats
Date: Mon, 11 Mar 2024 19:10:50 +0200
Organization: A noiseless patient Spider
Lines: 99
Message-ID: <20240311191050.0000030a@yahoo.com>
References: <usg40i$1udfo$3@dont-email.me>
	<Qry*XE3Ez@news.chiark.greenend.org.uk>
	<7da2a6f0e0878f914dee2286db833dc2@www.novabbs.org>
	<Qry*d14Ez@news.chiark.greenend.org.uk>
	<bd0b3b879184fd66b2c90cf4da2491a1@www.novabbs.org>
	<Rry*LM7Ez@news.chiark.greenend.org.uk>
	<20240311161009.00000923@yahoo.com>
	<vSEHN.170443$JLvf.69218@fx44.iad>
	<20240311171818.000073f6@yahoo.com>
	<20240311173250.0000096e@yahoo.com>
	<k8GHN.112717$Iswd.112514@fx05.iad>
	<20240311183907.00004589@yahoo.com>
	<wHGHN.481213$PuZ9.47608@fx11.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: dont-email.me; posting-host="20135147cba2d202cd079ad5c3141fdd";
	logging-data="3784551"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19oKyEZy9uyLo+OgsjbqksYDXPmWCOWweg="
Cancel-Lock: sha1:sTWjNniijMqL5x7UcwAFCN3U7a4=
X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
Bytes: 4848

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

> Michael S <already5chosen@yahoo.com> writes:
> >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 ?
> >  
> 
> RFC 1036
> 
> 2.1.2.  Date
> 
>     The "Date" line (formerly "Posted") is the date that the message
> was originally posted to the network.  Its format must be acceptable
>     both in RFC-822 and to the getdate(3) routine that is provided
> with the Usenet software.  This date remains unchanged as the message
> is propagated throughout the network.  One format that is acceptable
> to both is:
> 
>                       Wdy, DD Mon YY HH:MM:SS TIMEZONE
> 
>     Several examples of valid dates appear in the sample message
> above. Note in particular that ctime(3) format:
> 
>                           Wdy Mon DD HH:MM:SS YYYY
> 
>     is not acceptable because it is not a valid RFC-822 date.
> However, since older software still generates this format, news
>     implementations are encouraged to accept this format and translate
>     it into an acceptable format.
> 
> Granted, it is US centric.    Personnaly, I prefer sortable
> dates (YYYY MM DD).

Do you want to report the bug?
If you don't, I'd try to do it myself when back at home, but you seem
to be able to do it in more authoritative manner.