Read messages return to the new message list

Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build 14.0.8050.1202

I use WLMail as my default newsreader - and I subscribe to several
newsgroups on the server at msnews.microsoft.com.

I had previously used Outlook Express as my default newsreader. With
OE, the newsgroup synchronization settings were configured to download
headers only. This never led to any problems with OE, and I am using
the same settings in WLMail. However, I experienced a rather strange
phenomenon today, which affected one of the newsgroups only
(microsoft.public.windows.live.messenger).

When I started my computer this morning, I read all of the new messages
(in the preview pane). As I selected and read each message, the new
message count dwindled to zero.

As I read the messages, each one appeared in the list as having been
read. Exactly the same thing happened when I visited two other
newsgroups on the same server.

Having checked the messages, I closed WLMail and placed my computer into
Hibernation.

When, I returned to my computer, I noticed that the new message count on
this particular newsgroup had risen to 50+. When I checked the list, I
discovered that the messages that I had read six hours previously were
listed once again as new messages.

This only happened with the microsoft.public.windows.live.messenger
newsgroup. Rather than wade through the list again, I used the catch up
option.

Has anyone else experienced this problem and if so, I wonder whether
anyone can suggest how it might have happened?

I have the same problem only that I don't think the problem is restricted to
just one newsgroup.
I posted the question on 1/12 10:54 pm. I am still waiting for a reply.
t-4-2

"Bob Lucas" <> wrote in message
news:87E85331-C5FC-476F-B21A-...
> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build 14.0.8050.1202
>
> I use WLMail as my default newsreader - and I subscribe to several
> newsgroups on the server at msnews.microsoft.com.
>
> I had previously used Outlook Express as my default newsreader. With OE,
> the newsgroup synchronization settings were configured to download headers
> only. This never led to any problems with OE, and I am using the same
> settings in WLMail. However, I experienced a rather strange phenomenon
> today, which affected one of the newsgroups only
> (microsoft.public.windows.live.messenger).
>
> When I started my computer this morning, I read all of the new messages
> (in the preview pane). As I selected and read each message, the new
> message count dwindled to zero.
>
> As I read the messages, each one appeared in the list as having been read.
> Exactly the same thing happened when I visited two other newsgroups on the
> same server.
>
> Having checked the messages, I closed WLMail and placed my computer into
> Hibernation.
>
> When, I returned to my computer, I noticed that the new message count on
> this particular newsgroup had risen to 50+. When I checked the list, I
> discovered that the messages that I had read six hours previously were
> listed once again as new messages.
>
> This only happened with the microsoft.public.windows.live.messenger
> newsgroup. Rather than wade through the list again, I used the catch up
> option.
>
> Has anyone else experienced this problem and if so, I wonder whether
> anyone can suggest how it might have happened?
>
>
>
>

Do you have a 'Recovered items' folder under Storage folders? Any
sign of those duplicate messages in there? I have seen this
occasionally; I think it happens when the program has not had chance
to do its housekeeping on close-down. Could it be that you set the
machine to hibernate immediately after closing down WLMail? I can
see that, although the program interface disappears on close-down,
if I check what my AV is up to, I can see that it's still checking
WLMail files for some time afterwards. This is presumably writing
changes to the database from the log files, and if that process gets
interrupted, you may experience the phenomenon you describe. It's
annoying, but not life-threatening.

This is pure speculation on my part, and perhaps someone more
knowledgeable about the app's internal workings will be along with
something more meaty. If my supposed scenario is anything like true,
though, it's a bug, because hibernation should not cause the program
to malfunction. The most it calls for is a post-close 'Saving your
changes...' screen just like when Windows (XP) closes down.
--
Noel

"Bob Lucas" <> wrote in message
news:87E85331-C5FC-476F-B21A-...
> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build
> 14.0.8050.1202
>
> I use WLMail as my default newsreader - and I subscribe to several
> newsgroups on the server at msnews.microsoft.com.
>
> I had previously used Outlook Express as my default newsreader.
> With OE, the newsgroup synchronization settings were configured to
> download headers only. This never led to any problems with OE,
> and I am using the same settings in WLMail. However, I
> experienced a rather strange phenomenon today, which affected one
> of the newsgroups only (microsoft.public.windows.live.messenger).
>
> When I started my computer this morning, I read all of the new
> messages (in the preview pane). As I selected and read each
> message, the new message count dwindled to zero.
>
> As I read the messages, each one appeared in the list as having
> been read. Exactly the same thing happened when I visited two
> other newsgroups on the same server.
>
> Having checked the messages, I closed WLMail and placed my
> computer into Hibernation.
>
> When, I returned to my computer, I noticed that the new message
> count on this particular newsgroup had risen to 50+. When I
> checked the list, I discovered that the messages that I had read
> six hours previously were listed once again as new messages.
>
> This only happened with the
> microsoft.public.windows.live.messenger newsgroup. Rather than
> wade through the list again, I used the catch up option.
>
> Has anyone else experienced this problem and if so, I wonder
> whether anyone can suggest how it might have happened?
>
>
>
>

Thank you.

That is certainly a possible explanation and for the record, I have
found the following folders under 'Recovered Items'.

01-10-2009 11-38-01
01-10-2009 19-39-48
01-12-2009 10-22-56
01-13-2009 15-08-27
01-13-2009 17-50-43
01-14-2009 08-26-58

Each of these folders was empty (so I have deleted them).

Another possible explanation occurs to me. Could Microsoft have
undertaken maintenance on the server that carries this particular
newsgroup. If Microsoft have re-set identity numbering of messages on
the server, many newsreaders would treat them as new messages.

As you say, the phenomenon is annoying, but not life-threatening.
Incidentally, it did not recur, when I started WLMail this morning.





"Ildhund" <> wrote in message
news:#...
> Do you have a 'Recovered items' folder under Storage folders? Any sign
> of those duplicate messages in there? I have seen this occasionally; I
> think it happens when the program has not had chance to do its
> housekeeping on close-down. Could it be that you set the machine to
> hibernate immediately after closing down WLMail? I can see that,
> although the program interface disappears on close-down, if I check
> what my AV is up to, I can see that it's still checking WLMail files
> for some time afterwards. This is presumably writing changes to the
> database from the log files, and if that process gets interrupted, you
> may experience the phenomenon you describe. It's annoying, but not
> life-threatening.
>
> This is pure speculation on my part, and perhaps someone more
> knowledgeable about the app's internal workings will be along with
> something more meaty. If my supposed scenario is anything like true,
> though, it's a bug, because hibernation should not cause the program
> to malfunction. The most it calls for is a post-close 'Saving your
> changes...' screen just like when Windows (XP) closes down.
> --
> Noel
>
> "Bob Lucas" <> wrote in message
> news:87E85331-C5FC-476F-B21A-...
>> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build
>> 14.0.8050.1202
>>
>> I use WLMail as my default newsreader - and I subscribe to several
>> newsgroups on the server at msnews.microsoft.com.
>>
>> I had previously used Outlook Express as my default newsreader. With
>> OE, the newsgroup synchronization settings were configured to
>> download headers only. This never led to any problems with OE, and I
>> am using the same settings in WLMail. However, I experienced a
>> rather strange phenomenon today, which affected one of the newsgroups
>> only (microsoft.public.windows.live.messenger).
>>
>> When I started my computer this morning, I read all of the new
>> messages (in the preview pane). As I selected and read each message,
>> the new message count dwindled to zero.
>>
>> As I read the messages, each one appeared in the list as having been
>> read. Exactly the same thing happened when I visited two other
>> newsgroups on the same server.
>>
>> Having checked the messages, I closed WLMail and placed my computer
>> into Hibernation.
>>
>> When, I returned to my computer, I noticed that the new message count
>> on this particular newsgroup had risen to 50+. When I checked the
>> list, I discovered that the messages that I had read six hours
>> previously were listed once again as new messages.
>>
>> This only happened with the microsoft.public.windows.live.messenger
>> newsgroup. Rather than wade through the list again, I used the catch
>> up option.
>>
>> Has anyone else experienced this problem and if so, I wonder whether
>> anyone can suggest how it might have happened?
>>
>>
>>
>>

The fact that they were empty indicates that the messages they
contained have indeed been re-indexed properly, so all is as it
should be. How do the time stamps compare with your recollection of
setting the machine to hibernate or restarting it? If yesterday's
match what you wrote in your OP, then it looks like the recovery
takes place on start-up and the re-indexing on shut-down.

The workaround is 'wait a bit after shutting the program down before
hibernating'. If you set the compaction frequency to 1, you will get
notification that housekeeping is completed in the form of the
dialogue asking if you want to recover unused disk space. Dismiss it
(unless you want to do a compaction, of course) and hibernate
safely.
--
Noel

"Bob Lucas" <> wrote in message
news:1B3DC72A-A945-4826-8617-...
> Thank you.
>
> That is certainly a possible explanation and for the record, I
> have found the following folders under 'Recovered Items'.
>
> 01-10-2009 11-38-01
> 01-10-2009 19-39-48
> 01-12-2009 10-22-56
> 01-13-2009 15-08-27
> 01-13-2009 17-50-43
> 01-14-2009 08-26-58
>
> Each of these folders was empty (so I have deleted them).
>
> Another possible explanation occurs to me. Could Microsoft have
> undertaken maintenance on the server that carries this particular
> newsgroup. If Microsoft have re-set identity numbering of
> messages on the server, many newsreaders would treat them as new
> messages.
>
> As you say, the phenomenon is annoying, but not life-threatening.
> Incidentally, it did not recur, when I started WLMail this
> morning.
>
>
>
>
>
> "Ildhund" <> wrote in message
> news:#...
>> Do you have a 'Recovered items' folder under Storage folders? Any
>> sign of those duplicate messages in there? I have seen this
>> occasionally; I think it happens when the program has not had
>> chance to do its housekeeping on close-down. Could it be that you
>> set the machine to hibernate immediately after closing down
>> WLMail? I can see that, although the program interface disappears
>> on close-down, if I check what my AV is up to, I can see that
>> it's still checking WLMail files for some time afterwards. This
>> is presumably writing changes to the database from the log files,
>> and if that process gets interrupted, you may experience the
>> phenomenon you describe. It's annoying, but not life-threatening.
>>
>> This is pure speculation on my part, and perhaps someone more
>> knowledgeable about the app's internal workings will be along
>> with something more meaty. If my supposed scenario is anything
>> like true, though, it's a bug, because hibernation should not
>> cause the program to malfunction. The most it calls for is a
>> post-close 'Saving your changes...' screen just like when Windows
>> (XP) closes down.
>> --
>> Noel
>>
>> "Bob Lucas" <> wrote in message
>> news:87E85331-C5FC-476F-B21A-...
>>> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build
>>> 14.0.8050.1202
>>>
>>> I use WLMail as my default newsreader - and I subscribe to
>>> several newsgroups on the server at msnews.microsoft.com.
>>>
>>> I had previously used Outlook Express as my default newsreader.
>>> With OE, the newsgroup synchronization settings were configured
>>> to download headers only. This never led to any problems with
>>> OE, and I am using the same settings in WLMail. However, I
>>> experienced a rather strange phenomenon today, which affected
>>> one of the newsgroups only
>>> (microsoft.public.windows.live.messenger).
>>>
>>> When I started my computer this morning, I read all of the new
>>> messages (in the preview pane). As I selected and read each
>>> message, the new message count dwindled to zero.
>>>
>>> As I read the messages, each one appeared in the list as having
>>> been read. Exactly the same thing happened when I visited two
>>> other newsgroups on the same server.
>>>
>>> Having checked the messages, I closed WLMail and placed my
>>> computer into Hibernation.
>>>
>>> When, I returned to my computer, I noticed that the new message
>>> count on this particular newsgroup had risen to 50+. When I
>>> checked the list, I discovered that the messages that I had read
>>> six hours previously were listed once again as new messages.
>>>
>>> This only happened with the
>>> microsoft.public.windows.live.messenger newsgroup. Rather than
>>> wade through the list again, I used the catch up option.
>>>
>>> Has anyone else experienced this problem and if so, I wonder
>>> whether anyone can suggest how it might have happened?
>>>
>>>
>>>
>>>

Sorry, I forgot to address your second point. As far as I can see,
posts to MSNews are assigned a serial number as well as a message
ID. Yours get two serial numbers, because they're also passing
through the 'Communities support features' server. If you turn off
threading (Alt-V V) and look at the source (Ctrl-F3) of Winston's
latest burst of posts, you will see that they are neatly numbered
from 274638 to 274644, and that number is then used as the second
half of the .nws file name (in hex). Those numbers are, I think, set
in concrete.
If your theory about resetting the NG were true, then every
subscriber accessing the same server would see the same sort of
behaviour, yet there are only two posts about it!
--
Noel

"Bob Lucas" <> wrote in message
news:1B3DC72A-A945-4826-8617-...
> Thank you.
>
> That is certainly a possible explanation and for the record, I
> have found the following folders under 'Recovered Items'.
>
> 01-10-2009 11-38-01
> 01-10-2009 19-39-48
> 01-12-2009 10-22-56
> 01-13-2009 15-08-27
> 01-13-2009 17-50-43
> 01-14-2009 08-26-58
>
> Each of these folders was empty (so I have deleted them).
>
> Another possible explanation occurs to me. Could Microsoft have
> undertaken maintenance on the server that carries this particular
> newsgroup. If Microsoft have re-set identity numbering of
> messages on the server, many newsreaders would treat them as new
> messages.
>
> As you say, the phenomenon is annoying, but not life-threatening.
> Incidentally, it did not recur, when I started WLMail this
> morning.
>
>
>
>
>
> "Ildhund" <> wrote in message
> news:#...
>> Do you have a 'Recovered items' folder under Storage folders? Any
>> sign of those duplicate messages in there? I have seen this
>> occasionally; I think it happens when the program has not had
>> chance to do its housekeeping on close-down. Could it be that you
>> set the machine to hibernate immediately after closing down
>> WLMail? I can see that, although the program interface disappears
>> on close-down, if I check what my AV is up to, I can see that
>> it's still checking WLMail files for some time afterwards. This
>> is presumably writing changes to the database from the log files,
>> and if that process gets interrupted, you may experience the
>> phenomenon you describe. It's annoying, but not life-threatening.
>>
>> This is pure speculation on my part, and perhaps someone more
>> knowledgeable about the app's internal workings will be along
>> with something more meaty. If my supposed scenario is anything
>> like true, though, it's a bug, because hibernation should not
>> cause the program to malfunction. The most it calls for is a
>> post-close 'Saving your changes...' screen just like when Windows
>> (XP) closes down.
>> --
>> Noel
>>
>> "Bob Lucas" <> wrote in message
>> news:87E85331-C5FC-476F-B21A-...
>>> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build
>>> 14.0.8050.1202
>>>
>>> I use WLMail as my default newsreader - and I subscribe to
>>> several newsgroups on the server at msnews.microsoft.com.
>>>
>>> I had previously used Outlook Express as my default newsreader.
>>> With OE, the newsgroup synchronization settings were configured
>>> to download headers only. This never led to any problems with
>>> OE, and I am using the same settings in WLMail. However, I
>>> experienced a rather strange phenomenon today, which affected
>>> one of the newsgroups only
>>> (microsoft.public.windows.live.messenger).
>>>
>>> When I started my computer this morning, I read all of the new
>>> messages (in the preview pane). As I selected and read each
>>> message, the new message count dwindled to zero.
>>>
>>> As I read the messages, each one appeared in the list as having
>>> been read. Exactly the same thing happened when I visited two
>>> other newsgroups on the same server.
>>>
>>> Having checked the messages, I closed WLMail and placed my
>>> computer into Hibernation.
>>>
>>> When, I returned to my computer, I noticed that the new message
>>> count on this particular newsgroup had risen to 50+. When I
>>> checked the list, I discovered that the messages that I had read
>>> six hours previously were listed once again as new messages.
>>>
>>> This only happened with the
>>> microsoft.public.windows.live.messenger newsgroup. Rather than
>>> wade through the list again, I used the catch up option.
>>>
>>> Has anyone else experienced this problem and if so, I wonder
>>> whether anyone can suggest how it might have happened?
>>>
>>>
>>>
>>>

I leave WLM running and hibernate the computer.
I haven't noticed any problems.
--
Ronald Sommer

"Ildhund" <> wrote in message
news:...
> The fact that they were empty indicates that the messages they contained
> have indeed been re-indexed properly, so all is as it should be. How do
> the time stamps compare with your recollection of setting the machine to
> hibernate or restarting it? If yesterday's match what you wrote in your
> OP, then it looks like the recovery takes place on start-up and the
> re-indexing on shut-down.
>
> The workaround is 'wait a bit after shutting the program down before
> hibernating'. If you set the compaction frequency to 1, you will get
> notification that housekeeping is completed in the form of the dialogue
> asking if you want to recover unused disk space. Dismiss it (unless you
> want to do a compaction, of course) and hibernate safely.
> --
> Noel
>
> "Bob Lucas" <> wrote in message
> news:1B3DC72A-A945-4826-8617-...
>> Thank you.
>>
>> That is certainly a possible explanation and for the record, I have found
>> the following folders under 'Recovered Items'.
>>
>> 01-10-2009 11-38-01
>> 01-10-2009 19-39-48
>> 01-12-2009 10-22-56
>> 01-13-2009 15-08-27
>> 01-13-2009 17-50-43
>> 01-14-2009 08-26-58
>>
>> Each of these folders was empty (so I have deleted them).
>>
>> Another possible explanation occurs to me. Could Microsoft have
>> undertaken maintenance on the server that carries this particular
>> newsgroup. If Microsoft have re-set identity numbering of messages on
>> the server, many newsreaders would treat them as new messages.
>>
>> As you say, the phenomenon is annoying, but not life-threatening.
>> Incidentally, it did not recur, when I started WLMail this morning.
>>
>>
>>
>>
>>
>> "Ildhund" <> wrote in message
>> news:#...
>>> Do you have a 'Recovered items' folder under Storage folders? Any sign
>>> of those duplicate messages in there? I have seen this occasionally; I
>>> think it happens when the program has not had chance to do its
>>> housekeeping on close-down. Could it be that you set the machine to
>>> hibernate immediately after closing down WLMail? I can see that,
>>> although the program interface disappears on close-down, if I check what
>>> my AV is up to, I can see that it's still checking WLMail files for some
>>> time afterwards. This is presumably writing changes to the database from
>>> the log files, and if that process gets interrupted, you may experience
>>> the phenomenon you describe. It's annoying, but not life-threatening.
>>>
>>> This is pure speculation on my part, and perhaps someone more
>>> knowledgeable about the app's internal workings will be along with
>>> something more meaty. If my supposed scenario is anything like true,
>>> though, it's a bug, because hibernation should not cause the program to
>>> malfunction. The most it calls for is a post-close 'Saving your
>>> changes...' screen just like when Windows (XP) closes down.
>>> --
>>> Noel
>>>
>>> "Bob Lucas" <> wrote in message
>>> news:87E85331-C5FC-476F-B21A-...
>>>> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build 14.0.8050.1202
>>>>
>>>> I use WLMail as my default newsreader - and I subscribe to several
>>>> newsgroups on the server at msnews.microsoft.com.
>>>>
>>>> I had previously used Outlook Express as my default newsreader. With
>>>> OE, the newsgroup synchronization settings were configured to download
>>>> headers only. This never led to any problems with OE, and I am using
>>>> the same settings in WLMail. However, I experienced a rather strange
>>>> phenomenon today, which affected one of the newsgroups only
>>>> (microsoft.public.windows.live.messenger).
>>>>
>>>> When I started my computer this morning, I read all of the new messages
>>>> (in the preview pane). As I selected and read each message, the new
>>>> message count dwindled to zero.
>>>>
>>>> As I read the messages, each one appeared in the list as having been
>>>> read. Exactly the same thing happened when I visited two other
>>>> newsgroups on the same server.
>>>>
>>>> Having checked the messages, I closed WLMail and placed my computer
>>>> into Hibernation.
>>>>
>>>> When, I returned to my computer, I noticed that the new message count
>>>> on this particular newsgroup had risen to 50+. When I checked the
>>>> list, I discovered that the messages that I had read six hours
>>>> previously were listed once again as new messages.
>>>>
>>>> This only happened with the microsoft.public.windows.live.messenger
>>>> newsgroup. Rather than wade through the list again, I used the catch
>>>> up option.
>>>>
>>>> Has anyone else experienced this problem and if so, I wonder whether
>>>> anyone can suggest how it might have happened?
>>>>
>>>>
>>>>
>>>>

So do I, and nor have I. Even an ongoing Send/receive delays hibernation
until it's finished. It's just that 'limbo' period between closing down and
the program finishing its business that's tricky. The program is not in a
state that can successfully be written to disk ready to resume on wake-up.
IOW, it's a bug. Perhaps Bob will open a support ticket, which is about the
only way to report bugs at this stage in the program's life cycle (apart from
Feedback, which has the disadvantage of no feedback the other way).
--
Noel

"Ron Sommer" wrote:

> I leave WLM running and hibernate the computer.
> I haven't noticed any problems.
> --
> Ronald Sommer
>
> "Ildhund" <> wrote in message
> news:...
> > The fact that they were empty indicates that the messages they contained
> > have indeed been re-indexed properly, so all is as it should be. How do
> > the time stamps compare with your recollection of setting the machine to
> > hibernate or restarting it? If yesterday's match what you wrote in your
> > OP, then it looks like the recovery takes place on start-up and the
> > re-indexing on shut-down.
> >
> > The workaround is 'wait a bit after shutting the program down before
> > hibernating'. If you set the compaction frequency to 1, you will get
> > notification that housekeeping is completed in the form of the dialogue
> > asking if you want to recover unused disk space. Dismiss it (unless you
> > want to do a compaction, of course) and hibernate safely.
> > --
> > Noel
> >
> > "Bob Lucas" <> wrote in message
> > news:1B3DC72A-A945-4826-8617-...
> >> Thank you.
> >>
> >> That is certainly a possible explanation and for the record, I have found
> >> the following folders under 'Recovered Items'.
> >>
> >> 01-10-2009 11-38-01
> >> 01-10-2009 19-39-48
> >> 01-12-2009 10-22-56
> >> 01-13-2009 15-08-27
> >> 01-13-2009 17-50-43
> >> 01-14-2009 08-26-58
> >>
> >> Each of these folders was empty (so I have deleted them).
> >>
> >> Another possible explanation occurs to me. Could Microsoft have
> >> undertaken maintenance on the server that carries this particular
> >> newsgroup. If Microsoft have re-set identity numbering of messages on
> >> the server, many newsreaders would treat them as new messages.
> >>
> >> As you say, the phenomenon is annoying, but not life-threatening.
> >> Incidentally, it did not recur, when I started WLMail this morning.
> >>
> >>
> >>
> >>
> >>
> >> "Ildhund" <> wrote in message
> >> news:#...
> >>> Do you have a 'Recovered items' folder under Storage folders? Any sign
> >>> of those duplicate messages in there? I have seen this occasionally; I
> >>> think it happens when the program has not had chance to do its
> >>> housekeeping on close-down. Could it be that you set the machine to
> >>> hibernate immediately after closing down WLMail? I can see that,
> >>> although the program interface disappears on close-down, if I check what
> >>> my AV is up to, I can see that it's still checking WLMail files for some
> >>> time afterwards. This is presumably writing changes to the database from
> >>> the log files, and if that process gets interrupted, you may experience
> >>> the phenomenon you describe. It's annoying, but not life-threatening.
> >>>
> >>> This is pure speculation on my part, and perhaps someone more
> >>> knowledgeable about the app's internal workings will be along with
> >>> something more meaty. If my supposed scenario is anything like true,
> >>> though, it's a bug, because hibernation should not cause the program to
> >>> malfunction. The most it calls for is a post-close 'Saving your
> >>> changes...' screen just like when Windows (XP) closes down.
> >>> --
> >>> Noel
> >>>
> >>> "Bob Lucas" <> wrote in message
> >>> news:87E85331-C5FC-476F-B21A-...
> >>>> Win XP Pro (SP3) with IE7 and WLMail 2009 version, Build 14.0.8050.1202
> >>>>
> >>>> I use WLMail as my default newsreader - and I subscribe to several
> >>>> newsgroups on the server at msnews.microsoft.com.
> >>>>
> >>>> I had previously used Outlook Express as my default newsreader. With
> >>>> OE, the newsgroup synchronization settings were configured to download
> >>>> headers only. This never led to any problems with OE, and I am using
> >>>> the same settings in WLMail. However, I experienced a rather strange
> >>>> phenomenon today, which affected one of the newsgroups only
> >>>> (microsoft.public.windows.live.messenger).
> >>>>
> >>>> When I started my computer this morning, I read all of the new messages
> >>>> (in the preview pane). As I selected and read each message, the new
> >>>> message count dwindled to zero.
> >>>>
> >>>> As I read the messages, each one appeared in the list as having been
> >>>> read. Exactly the same thing happened when I visited two other
> >>>> newsgroups on the same server.
> >>>>
> >>>> Having checked the messages, I closed WLMail and placed my computer
> >>>> into Hibernation.
> >>>>
> >>>> When, I returned to my computer, I noticed that the new message count
> >>>> on this particular newsgroup had risen to 50+. When I checked the
> >>>> list, I discovered that the messages that I had read six hours
> >>>> previously were listed once again as new messages.
> >>>>
> >>>> This only happened with the microsoft.public.windows.live.messenger
> >>>> newsgroup. Rather than wade through the list again, I used the catch
> >>>> up option.
> >>>>
> >>>> Has anyone else experienced this problem and if so, I wonder whether
> >>>> anyone can suggest how it might have happened?
> >>>>
> >>>>
> >>>>
> >>>>
>