From: "Robert Comer" 

> IIRC news is usually bounced about the world from server to server. So
> which server should the 'sent' time come from? What if the server you're
> viewing on gets replies via different paths?

The time should be whatever server it got posted to first.

> which makes sense.

Not to me, not when there's only one main server.

Anyway, you're right, OE is not specifically to blame, but the NNTP is. 
The assumption of the client setting the time/date of the post is what I
don't like.

>Are those 'right'? Since October Geo's gone from -0400 to -0600 which looks
>like a double correction for DST to me...

Nope, they are not "right" because the frame of reference is different.

- Bob Comer


"Paul Ranson"  wrote in message
news:418f69d6$1{at}w3.nls.net...
>I doubt you can blame OE for this.
>
> IIRC news is usually bounced about the world from server to server. So
> which server should the 'sent' time come from? What if the server you're
> viewing on gets replies via different paths?
>
> Anyway Antti's message has a 'date' header,
>
> Date: Sun, 7 Nov 2004 16:56:48 +0200
>
> which makes sense. It displays as 14.56 here which also makes sense. Geo's
> message is -0600 and Bob's -0500. Are those 'right'? Since October Geo's
> gone from -0400 to -0600 which looks like a double correction for DST to
> me...
>
> Paul
>
> "Antti Kurenniemi" 
wrote in message
> news:418e35c7{at}w3.nls.net...
>> "Robert Comer"  wrote in message
>> news:418e0b31$1{at}w3.nls.net...
>>> >Or is it OE that does some "fancy" stuff and messes it up?
>>>
>>> Bingo.  The timestamp comes from the posting machines, and OE does some
>>> fancy timezone stuff that totally messes things up.
>>
>> Stupid. A perfectly valid approach is to just use the server time and
>> everything's in proper order, but noooo, have to be clever...
>>
>>
>> Antti Kurenniemi
>> (grrrrrr)
>>
>>
>
>

--- BBBS/NT v4.01 Flag-5