[SpamCop-List] Re: What else can I do?

[Mike Easter]

Bud wrote:

> I don't know how this got duplicated

Sometimes it is interesting to compare the msgid/s and timestamp/s, and
sometimes it isn't.

Date: Fri, 2 Dec 2005 15:31:46 -0800
Message-ID: <dmqlkd$p48$1 at news.spamcop.net>
NNTP-Posting-Date: Fri, 2 Dec 2005 23:33:33 +0000 (UTC)

Date: Fri, 2 Dec 2005 15:33:32 -0800
Message-ID: <dmqlkd$p48$2 at news.spamcop.net>
NNTP-Posting-Date: Fri, 2 Dec 2005 23:33:34 +0000 (UTC)

The only thing which is interesting to me about the comparison is the
difference in seconds between the nntp date stamped by the server and
the date stamped by your machine.

Your machine sez a difference of 1min 46sec -- whereas the nntp stamp
sez a difference of 1 sec.

You would expect a hiccup to have closer times on your end than the
newsserver's - I would think.

Some people's news agents, I think OE does this, put stamp the item
based on when the person starts editing the item.  At least I think I
formed that theory once upon a time when I was being the volunteer clock
police person and would pull Ellen over for clock discrepancies.

It seemed that the explanation was not based on her clock being set
wrong, but the fact that she sometimes starts a news message and
finishes it later and then posts it.  Or something like that, I think.

OTOH, if you were trying to imagine a scenario to make a longer time for
your agent vs the newsserver, you would have your agent *not* stamping
its time until it got 'hooked up' with the server.  So, if it were
having a delay in the hookup, then it would be waiting and waiting to
get hooked up, and while it was waiting it would hiccup.  Then, in the
same second as the hiccup the agent and server hooked up - like hookup
plus hiccup - and then the server would get 'both' of them almost
simultaneously, ie 1 second apart.

But, that scenario doesn't fit with my current concept of how a message
gets dated by the user's agent.

My provider's newsserver changes my date to its own, which annoys me as
a newsserver behavior.  I think it should leave it alone.

-- 
Mike Easter
kibitzer, not SC admin