Doum said:
Why are you starting a new thread?
We don't know who you're answering to and we cannot follow up his thread.
New threads (solo or starter articles) do NOT have a References header.
This header lists the series of articles in a [sub]thread. Notice there
is a References header in Jim's post. That means Jim *was* replying to
another post. In Jim's reply was:
References: <
[email protected]>
That means Jim was REPLYING to an article whose Message-ID was the value
shown above. Something is screwed up with YOUR newsreader (XNews) or
the NNTP server to which you connect (Microsoft's) is screwed up in its
article database (you can't find the article) or in their overview
database (the article shows up in a header list pane but you cannot
retrieve the article).
"blues music fan" posts on 7/26/10
Message-ID: <
[email protected]>
Jim replies on 7/27/10
Message-ID: <
[email protected]>
References: <
[email protected]>
Notice each message has its own unique message ID (MID). Also notice
that the References header in Jim's reply lists bluesmusicfan's MID. If
the subthread were longer, there would be more MIDs listed in the
References header to track that subthread's hierarchy of posts.
I've been caught on this in the past, too, where I thought someone was
starting a new thread as their reply instead of replying to an existing
thread. To make sure I don't do that blunder, I look at the headers to
see if there is a References header. If there, it was a proper reply
(although the original article might be so old that your server no
longer carries it beyond their retention interval). In this case, the
original post was submitted yesterday so it should still be on the NNTP
server you use.
My guess is that you have threading or grouping misconfigured in Xnews
so you end up seeing lots of orphaned replies. For help with Xnews, ask
the folks over in the news.software.readers group. You've been posting
long enough with Xnews that you should know how to configure its
threading or a view using grouping. I don't use Xnews to know if the
symptom you noticed is some corruption with your local message store for
Xnews or a problem with Microsoft's NNTP server (which I quit using long
ago due to problems with it in accepting some otherwise legit posts).