🚀 go-pugleaf

"Alan Bellingham" <alanb@episys.com> wrote in message
news:cbqnr1l23dbibhkdk7c78lsdjf39o0t0rl@4ax.com...
>
> If the sender doesn't set a timestamp, then the first server that
deals
> with it should. And the timestamp should, of course, indicate the time
> zone.
>
> For instance, your message was marked as:
>
>   Date: Wed, 4 Jan 2006 08:58:55 -0800
>
> which I see as 04/01/2006 16:58:55. Bruce's message, interestingly,
had
> a different timezone. Since both your messages arrived via the same
> single news server, one knows that at least one of your clients is
> correctly adding the timestamp itself - and probably both.
>
> The time associated with a message is usually that of the client PCs,
> rather than that of the server. This does mean that any PC with an
> incorrectly set clock (e.g. anyone with a Windows PC who accepts the
> default time zone without actually being in that timezone, for
example)
> will have misdated messages.
>
> (There are also propagation issues - anyone who assumes that they will
> see a newsgroup message instantly is naive or deluded.)
>
> Alan Bellingham

does make sence to me. But what I can't figure out is according to Bruce
our messages on his system are shown as 7 min apart. My pc says:
    Bruce's post - 6:33 am
    Boba's       - 8:58 am
If all (or at least most of) time zones boundaries are based on int hour
values, how could the gap on my system become 15 min? Could it be what
you call a propagation issue?