OE not downloading messages when Watch is used
Paul
not all messages are being downloaded in that newsgroup during
synchronising.
Using a second identity in OE to download the same newsgroup
from the same news server but with no threads 'watched' - all
messages are downloaded.
The missing message problem appears to start once new messages
are downloaded to a watched thread - and gets worse after each
synchronising if new messages happen to be added to a
'Watched' thread.
None of this occurs if 'Watch' isn't used.
None of this happens if 'news.microsoft.com' is used - it only
occurs on my ISP's news server
It appears that OE checks specifically for watched messages
during synchronising so I wonder if this a known problem with
some news servers?
Thanks for any comment or advice ...Paul
PS -
'Get 300 Headers at a Time' is not checked
'Compact Messages in the Background' is not checked
PC is Win98SE, IE5.00.3105.0106, OE5.50.4133.2400
There are no obvious error or fail messages in a 'News' log
..and
getting out of my depth :)
Robert Aldwinckle
would expect to be able to get from it in this case (ideally) is to
compare how the two servers respond to the same requests. If you can
reproduce the symptom on a lightly used Test newsgroup it should be that
much easier to analyse.
If necessary you could simulate other posters using a second OE account
for the same server or, even better, use two servers which host the same
newsgroup. You would want to suppress any notification of activity in
your normal subscriptions while testing to keep your logs clean.
However, depending on how predictable this is, it may be that you are
just seeing a symptom of some normal posting propagation delay/ network
loss. (E.g. for msnews newsgroups, posting via msnews server has little
delay; posting via your ISP has who knows what delay depending on the
path and the average number of hops to the msnews server.)
Actually, I'm not exactly clear on what causes the propagation in this
case but I have a notion that a post may only arrive at the msnews
server by accident of a general broadcast rather than a directed push.
So then you have to worry also that in any intermediate servers the
administrators don't happen to have a cleanup task active that purges
newsgroups that they aren't particularly interested in. That happens
especially to newsgroups which don't fit in the "big 8" USENET
categories. And unfortunately, that could mean msnews newsgroups
postings (moving in either direction) get dropped.
Good luck
Robert Aldwinckle
---
"Paul" <paul...@btinternet.com> wrote in message
news:eLitbbNyAHA.1864@tkmsftngp03...
Paul
I attempted to use 'microsoft.public.test' on both
'news.microsoft.com' and 'news.btinternet.com' (my ISP's news
server). However, there were too many vagaries going on between
the same newsgroup on the different servers to get a consistent
set of messages on the two servers.
If it's any value, I set up two new OE Identities both
subscribed to 'btinternet.test' on the ISP's server and got both
OE Identites showing the same messages. In one OE Identity, two
threads were 'Watched' and in the other Identity no threads were
watched.
I then posted a couple of messages into the watched threads, a
couple into unwatched threads and posted a couple new messages
starting new threads. There were also a four or five messages
posted by others.
Enabling 'News' log on both the watched identity and the
unwatched identity (both still showing the same messages and all
messages marked 'Read') , I synchronised both identities using
'New messages only'
The 'Watched' identity didn't download four or five messages
(seemingly ignoring randomly some of the new messages posted)
while the 'unwatched' identity downloaded them all.
Current view was 'Show all messages'
Get 300 messages was unchecked
Compact in background was unchecked
No message rules in either identity
PC is Win98SE, IE5.00.3105.0106, OE5.50.4133.2400
My guess is it's a 'funny' with the ISP's server, perhaps
something to do with the article number handling(?) assuming
I'm not making a bad representation of what I see.
I've pasted the two 'news' logs below, but they look a mess with
line wrap
If it's a nightmare, don't hesitate to ignore this - I can live
with the problem by using Flag rather than Watch
Regards, ...Paul
******'News' log from 'unwatched' OE Identity******
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/21/2001 22:46:35
NNTP: 22:46:35 [db] Connecting to 'news.btinternet.com' on port
119.
NNTP: 22:46:52 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:46:52 [tx] MODE READER
NNTP: 22:46:52 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:46:52 [tx] GROUP btinternet.test
NNTP: 22:46:52 [rx] 211 193 52609 52801 btinternet.test
NNTP: 22:46:52 [db] Connection to 'news.btinternet.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/21/2001 22:46:52
NNTP: 22:46:52 [db] Connecting to 'news.btinternet.com' on port
119.
NNTP: 22:46:52 [rx] 200 plutonium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:46:52 [tx] MODE READER
NNTP: 22:46:52 [rx] 200 plutonium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:46:52 [tx] GROUP btinternet.test
NNTP: 22:46:53 [rx] 211 193 52609 52801 btinternet.test
NNTP: 22:46:53 [tx] XOVER 52790-52801
NNTP: 22:46:53 [rx] 224 data follows
NNTP: 22:46:53 [tx] ARTICLE 52790
NNTP: 22:46:53 [rx] 220 52790
<9bt2m8$2a5$1...@plutonium.btinternet.com> article
NNTP: 22:46:53 [tx] ARTICLE 52791
NNTP: 22:46:54 [rx] 220 52791
<9bt2mc$fob$1...@neptunium.btinternet.com> article
NNTP: 22:46:54 [tx] ARTICLE 52792
NNTP: 22:46:54 [rx] 220 52792
<9bt2me$fob$2...@neptunium.btinternet.com> article
NNTP: 22:46:54 [tx] ARTICLE 52793
NNTP: 22:46:54 [rx] 220 52793
<9bt2me$fob$3...@neptunium.btinternet.com> article
NNTP: 22:46:54 [tx] ARTICLE 52794
NNTP: 22:46:54 [rx] 220 52794
<9bt2ed$fec$1...@neptunium.btinternet.com> article
NNTP: 22:46:54 [tx] ARTICLE 52795
NNTP: 22:46:55 [rx] 220 52795
<9bt2h0$22j$1...@plutonium.btinternet.com> article
NNTP: 22:46:55 [tx] ARTICLE 52796
NNTP: 22:46:55 [rx] 220 52796
<9bt2kc$285$1...@plutonium.btinternet.com> article
NNTP: 22:46:55 [tx] ARTICLE 52797
NNTP: 22:46:55 [rx] 220 52797
<9bt2mf$fob$4...@neptunium.btinternet.com> article
NNTP: 22:46:55 [tx] ARTICLE 52798
NNTP: 22:46:55 [rx] 220 52798
<9bt2mg$fob$5...@neptunium.btinternet.com> article
NNTP: 22:46:55 [tx] ARTICLE 52799
NNTP: 22:46:55 [rx] 220 52799
<9bt2mh$fob$6...@neptunium.btinternet.com> article
NNTP: 22:46:55 [tx] ARTICLE 52800
NNTP: 22:46:56 [rx] 220 52800
<9bt2oq$fqq$1...@neptunium.btinternet.com> article
NNTP: 22:46:56 [tx] ARTICLE 52801
NNTP: 22:46:56 [rx] 220 52801
<9bt2pi$2fl$1...@plutonium.btinternet.com> article
NNTP: 22:46:56 [db] Connection to 'news.btinternet.com' closed.
*****'News' log from 'Watched' OE Identity*****
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/21/2001 22:47:14
NNTP: 22:47:14 [db] Connecting to 'news.btinternet.com' on port
119.
NNTP: 22:47:30 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:47:30 [tx] MODE READER
NNTP: 22:47:30 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:47:30 [tx] GROUP btinternet.test
NNTP: 22:47:30 [rx] 211 193 52609 52801 btinternet.test
NNTP: 22:47:30 [db] Connection to 'news.btinternet.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/21/2001 22:47:30
NNTP: 22:47:30 [db] Connecting to 'news.btinternet.com' on port
119.
NNTP: 22:47:47 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:47:47 [tx] MODE READER
NNTP: 22:47:47 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:47:47 [tx] GROUP btinternet.test
NNTP: 22:47:47 [rx] 211 193 52609 52801 btinternet.test
NNTP: 22:47:47 [tx] XHDR References 52790-52801
NNTP: 22:47:47 [rx] 221 References fields follow
NNTP: 22:47:47 [tx] XHDR Subject 52790-52801
NNTP: 22:47:47 [rx] 221 Subject fields follow
NNTP: 22:47:47 [tx] ARTICLE 52797
NNTP: 22:47:48 [rx] 220 52797
<9bt2mf$fob$4...@neptunium.btinternet.com> article
NNTP: 22:47:48 [tx] ARTICLE 52799
NNTP: 22:47:48 [rx] 220 52799
<9bt2mh$fob$6...@neptunium.btinternet.com> article
NNTP: 22:47:48 [db] Connection to 'news.btinternet.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/21/2001 22:47:48
NNTP: 22:47:48 [db] Connecting to 'news.btinternet.com' on port
119.
NNTP: 22:48:04 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:48:04 [tx] MODE READER
NNTP: 22:48:04 [rx] 200 neptunium.btinternet.com InterNetNews
NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 22:48:04 [tx] GROUP btinternet.test
NNTP: 22:48:04 [rx] 211 193 52609 52801 btinternet.test
NNTP: 22:48:04 [tx] XOVER 52800-52801
NNTP: 22:48:04 [rx] 224 data follows
NNTP: 22:48:04 [tx] ARTICLE 52800
NNTP: 22:48:04 [rx] 220 52800
<9bt2oq$fqq$1...@neptunium.btinternet.com> article
NNTP: 22:48:04 [tx] ARTICLE 52801
NNTP: 22:48:04 [rx] 220 52801
<9bt2pi$2fl$1...@plutonium.btinternet.com> article
NNTP: 22:48:04 [db] Connection to 'news.btinternet.com' closed.
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:OvZ2YeiyAHA.1796@tkmsftngp02...
> I don't think you would see an error message in the log. All
> that I would expect to be able to get from it in this case
> (ideally) is to compare how the two servers respond to the
same
> requests. If you can reproduce the symptom on a lightly used
> Test newsgroup it should be that much easier to analyse.
<snip>
> "Paul" <paul...@btinternet.com> wrote in message
> news:eLitbbNyAHA.1864@tkmsftngp03...
> > If I set 'Watch' on threads in a newsgroup, within a day or
> > two, not all messages are being downloaded in that
> > newsgroup during synchronising.
<snip>
Ron Sommer
You need to update IE.
--
Ron Sommer
"Paul" <pau...@btinternet.com> wrote in message news:#7mke$xyAHA.2208@tkmsftngp02...
Paul
reading the IE5.5 NG's or wait until I do a fresh Win98
re-install
and not use the IE5 SP1 OE upgrade option. (The PC is otherwise
stable, I can't recall the last freeze or 'crash')
I'm fairly new to IE/OE (previous Netscape user) and
now realise I mis-understood the IE5 SP1 upgrade.
Thanks for seeing that in a long message, ...Paul
"Ron Sommer" <rso...@nospam.ktis.net> wrote in message
news:#81v4DyyAHA.1352@tkmsftngp05...
This is not a recommend practice, IE5.00.3105.0106,
OE5.50.4133.2400.
You need to update IE.
--
Ron Sommer
"Paul" <pau...@btinternet.com> wrote in message
news:#7mke$xyAHA.2208@tkmsftngp02...
<snip>
> Current view was 'Show all messages'
> Get 300 messages was unchecked
> Compact in background was unchecked
> No message rules in either identity
> PC is Win98SE, IE5.00.3105.0106, OE5.50.4133.2400
Robert Aldwinckle
Nice Doc! I don't have time right now to investigate this thoroughly
but it looks to me that there are two things in your
"*****'News' log from 'Watched' OE Identity*****"
worth noting immediately.
"NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok)."
and (more importantly)
"NNTP: 22:48:04 [tx] XOVER 52800-52801"
after
"
NNTP: 22:47:47 [tx] XHDR References 52790-52801
NNTP: 22:47:47 [rx] 221 References fields follow
NNTP: 22:47:47 [tx] XHDR Subject 52790-52801
NNTP: 22:47:47 [rx] 221 Subject fields follow
"
First, the version of software running on your server is old. So my
guess is that there could be a miscommunication between it and the
client involving the meaning of these extension commands (not to mention
the implementation of them).
Second, we need to know what the definition of XHDR is, at least as OE
understands it. One way to do that would be to redo the same test that
you have just done, this time with the msnews server. (Pick a really
dead newsgroup; you have a good reason for not using Test.) My guess is
that you will find that one will be sending *all* the new headers and
not just some that match a list of references and subjects that are
given with the command. (That's a speculative inference that assumes
the second command that OE gave (the XOVER) was not an error on its
part.)
Here's where I will be going to try to find out /the facts/. (Excerpt
from an earlier post.)
<http://www.faqs.org/rfcs/rfc977.html>
<http://www.faqs.org/faqs/usenet/software/inn-faq/part1/>
FWIW I have lots of watched threads and usually don't see this feature.
(I have seen it but can't remember the exact circumstances.) A possible
workaround you might want to try is to use Synchronize All (e.g.
Ctrl-Shift-M) instead of Synchronize Newsgroup. That's what I normally
use and am pretty sure that the feature isn't used then. However, I
have "All Messages" set for my Synchronization Settings for all
subscriptions too; so that may be the real difference. If it is the
Synchronize All aspect that is doing it you could simulate a Sychronize
Newsgroup by /unchecking/ any other newsgroup's Synchronization settings
first. I'd be curious knowing which category /Synchronize Account/
falls into if this works because I used to use that.
Good luck
Robert
---
"Paul" <pau...@btinternet.com> wrote in message
news:#7mke$xyAHA.2208@tkmsftngp02...
[test results]
Paul
Two OE identies were synchronised so they contained the same
recent messages. One OE identity set with two threads 'watched'
- and the second OE identity with no threads watched.
'News log' was enabled and both OE identities were synchronised the
same way as before ( 'New messages only'). BTW, I click on the news
server name in the 'Folder' pane over on the left and use the
'Synchronize Account' button - and then swap identity for the second
synch.
Eight new messages downloaded into both the 'watched' and 'unwatched'
OE identities. Of the eight messages, one message went into each of
the two 'watched' threads (I'm not sure I like being this
definite<G>). The logs are pasted below.
A Google search for XHDR found this page titled
"NNTP-Ext 2.6 XHDR"-
http://www.mibsoftware.com/userkt/nntpext/0023.htm
It looks erm, looks concise
I haven't tried the different methods of synchronising as suggested
yet - if I can get anything consistent I'll post the details
Thanks again, ....Paul
**** The Unwatched News Log****
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:36
NNTP: 23:26:36 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:37 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:37 [tx] MODE READER
NNTP: 23:26:37 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:37 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:37 [rx] 211 10721 223 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:37 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:37
NNTP: 23:26:37 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:38 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:38 [tx] MODE READER
NNTP: 23:26:38 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:38 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:38 [rx] 211 10284 109708 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:38 [tx] XOVER 131687-131694
NNTP: 23:26:39 [rx] 224 Overview information follows
NNTP: 23:26:39 [tx] ARTICLE 131687
NNTP: 23:26:39 [rx] 220 131687 <OOH6PD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:39 [tx] ARTICLE 131688
NNTP: 23:26:40 [rx] 220 131688 <usf8fD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:40 [tx] ARTICLE 131689
NNTP: 23:26:41 [rx] 220 131689 <OGoJoD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:41 [tx] ARTICLE 131690
NNTP: 23:26:41 [rx] 220 131690 <uax75a3yAHA.2208@tkmsftngp02>
NNTP: 23:26:41 [tx] ARTICLE 131691
NNTP: 23:26:42 [rx] 220 131691 <E9IE6.235$f.3...@news1.cableinet.net>
NNTP: 23:26:42 [tx] ARTICLE 131692
NNTP: 23:26:42 [rx] 220 131692 <ugMAF33yAHA.2004@tkmsftngp02>
NNTP: 23:26:42 [tx] ARTICLE 131693
NNTP: 23:26:42 [rx] 220 131693 <eR7T#A4yAHA.904@tkmsftngp02>
NNTP: 23:26:42 [tx] ARTICLE 131694
NNTP: 23:26:43 [rx] 220 131694
<9qp6et8rm7cbf13ik...@4ax.com>
NNTP: 23:26:43 [db] Connection to 'news.microsoft.com' closed.
****The 'Watched' News Log****
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:03
NNTP: 23:26:03 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:03 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:03 [tx] MODE READER
NNTP: 23:26:03 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:03 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:04 [rx] 211 10721 223 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:04 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:04
NNTP: 23:26:04 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:04 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:04 [tx] MODE READER
NNTP: 23:26:05 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:05 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:05 [rx] 211 10284 109708 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:05 [tx] XHDR References 131687-131694
NNTP: 23:26:06 [rx] 221 Xhdr information follows
NNTP: 23:26:06 [tx] XHDR Subject 131687-131694
NNTP: 23:26:06 [rx] 221 Xhdr information follows
NNTP: 23:26:06 [tx] ARTICLE 131687
NNTP: 23:26:07 [rx] 220 131687 <OOH6PD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:07 [tx] ARTICLE 131688
NNTP: 23:26:07 [rx] 220 131688 <usf8fD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:07 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:07
NNTP: 23:26:07 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:08 [tx] MODE READER
NNTP: 23:26:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:08 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:08 [rx] 211 10284 109708 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:08 [tx] XOVER 131689-131694
NNTP: 23:26:09 [rx] 224 Overview information follows
NNTP: 23:26:09 [tx] ARTICLE 131689
NNTP: 23:26:09 [rx] 220 131689 <OGoJoD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:09 [tx] ARTICLE 131690
NNTP: 23:26:10 [rx] 220 131690 <uax75a3yAHA.2208@tkmsftngp02>
NNTP: 23:26:10 [tx] ARTICLE 131691
NNTP: 23:26:10 [rx] 220 131691 <E9IE6.235$f.3...@news1.cableinet.net>
NNTP: 23:26:10 [tx] ARTICLE 131692
NNTP: 23:26:11 [rx] 220 131692 <ugMAF33yAHA.2004@tkmsftngp02>
NNTP: 23:26:11 [tx] ARTICLE 131693
NNTP: 23:26:11 [rx] 220 131693 <eR7T#A4yAHA.904@tkmsftngp02>
NNTP: 23:26:11 [tx] ARTICLE 131694
NNTP: 23:26:12 [rx] 220 131694
<9qp6et8rm7cbf13ik...@4ax.com>
NNTP: 23:26:12 [db] Connection to 'news.microsoft.com' closed.
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:OzctA11yAHA.1256@tkmsftngp03...
I don't have time right now to investigate this thoroughly
but it looks to me that there are two things in your
"*****'News' log from 'Watched' OE Identity*****"
worth noting immediately.
<snip>
Second, we need to know what the definition of XHDR is, at least as
OE understands it. One way to do that would be to redo the same test
that you have just done, this time with the msnews server. (Pick a
really dead newsgroup; you have a good reason for not using Test.) My
guess
is that you will find that one will be sending *all* the new headers
and not just some that match a list of references and subjects that
are
given with the command. (That's a speculative inference that assumes
the second command that OE gave (the XOVER) was not an error on its
part.)
<snip>
Paul
Previously, I'd been using 'Synchronize Account'.
Using 'Synchronise All' combined with 'New messages only' seems
to avoid the problem. Can't quite believe it :)
I haven't tried any other combinations as this seems the 'workaround'.
However, I haven't been able to test this out using my normal NG list
yet
The procedure was the same a before. Subscribed to 'btinternet.test'
on 'news.btinternet.com'. Post eight new messages, two into 'Watched'
threads and using 'Synchronize All' (from the 'Tools' menu) and 'New
messages only' - all eight messages are successfully downloaded
I've done this twice in two different OE Identities. One of the logs
is pasted below, the second log was essentially the same
*Cheers* ....Paul
***News Log Using Watched, Synchronised All & New Messages Only***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/23/2001 08:48:25
NNTP: 08:48:25 [db] Connecting to 'news.btinternet.com' on port 119.
NNTP: 08:48:26 [rx] 200 neptunium.btinternet.com InterNetNews NNRP
server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 08:48:26 [tx] MODE READER
NNTP: 08:48:26 [rx] 200 neptunium.btinternet.com InterNetNews NNRP
server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 08:48:26 [tx] GROUP btinternet.test
NNTP: 08:48:26 [rx] 211 242 52633 52874 btinternet.test
NNTP: 08:48:26 [tx] XOVER 52867-52874
NNTP: 08:48:26 [rx] 224 data follows
NNTP: 08:48:27 [tx] ARTICLE 52867
NNTP: 08:48:27 [rx] 220 52867 <9c0pud$o7i$1...@uranium.btinternet.com>
article
NNTP: 08:48:27 [tx] ARTICLE 52868
NNTP: 08:48:27 [rx] 220 52868 <9c0pud$o7i$2...@uranium.btinternet.com>
article
NNTP: 08:48:27 [tx] ARTICLE 52869
NNTP: 08:48:27 [rx] 220 52869 <9c0q7a$j48$1...@plutonium.btinternet.com>
article
NNTP: 08:48:27 [tx] ARTICLE 52870
NNTP: 08:48:27 [rx] 220 52870 <9c0q7b$j48$2...@plutonium.btinternet.com>
article
NNTP: 08:48:28 [tx] ARTICLE 52871
NNTP: 08:48:28 [rx] 220 52871 <9c0q7b$j48$3...@plutonium.btinternet.com>
article
NNTP: 08:48:28 [tx] ARTICLE 52872
NNTP: 08:48:28 [rx] 220 52872 <9c0q7c$j48$4...@plutonium.btinternet.com>
article
NNTP: 08:48:28 [tx] ARTICLE 52873
NNTP: 08:48:28 [rx] 220 52873 <9c0q7c$j48$5...@plutonium.btinternet.com>
article
NNTP: 08:48:28 [tx] ARTICLE 52874
NNTP: 08:48:28 [rx] 220 52874 <9c0q7d$j48$6...@plutonium.btinternet.com>
article
NNTP: 08:48:28 [db] Connection to 'news.btinternet.com' closed.
----
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:OzctA11yAHA.1256@tkmsftngp03...
<snipped in an attempt to keep a long message short>
Paul
BTW, no rush at all - if there's anything to comment on
amongst about a thousand lines,
Cheers, ...Paul
The two successful logs are -
***First Profile
***Second Profile
***News Log Using Watched, Synchronised All & New Messages Only***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/23/2001 09:20:02
NNTP: 09:20:02 [db] Connecting to 'news.btinternet.com' on port 119.
NNTP: 09:20:02 [db] srv_name = "news.btinternet.com" srv_addr =
194.73.73.116
NNTP: 09:20:02 [rx] 200 uranium.btinternet.com InterNetNews NNRP
server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 09:20:02 [tx] MODE READER
NNTP: 09:20:02 [rx] 200 uranium.btinternet.com InterNetNews NNRP
server INN 1.5.1 17-Dec-1996 ready (posting ok).
NNTP: 09:20:02 [tx] GROUP btinternet.test
NNTP: 09:20:03 [rx] 211 251 52633 52883 btinternet.test
NNTP: 09:20:03 [tx] XOVER 52875-52883
NNTP: 09:20:03 [rx] 224 data follows
NNTP: 09:20:03 [tx] ARTICLE 52875
NNTP: 09:20:03 [rx] 220 52875 <9c0rku$h5t$7...@neptunium.btinternet.com>
article
NNTP: 09:20:03 [tx] ARTICLE 52876
NNTP: 09:20:04 [rx] 220 52876 <9c0rku$h5t$8...@neptunium.btinternet.com>
article
NNTP: 09:20:04 [tx] ARTICLE 52877
NNTP: 09:20:04 [rx] 220 52877 <9c0rkv$h5t$9...@neptunium.btinternet.com>
article
NNTP: 09:20:04 [tx] ARTICLE 52878
NNTP: 09:20:04 [rx] 220 52878 <9c0rkp$h5t$1...@neptunium.btinternet.com>
article
NNTP: 09:20:04 [tx] ARTICLE 52879
NNTP: 09:20:04 [rx] 220 52879 <9c0rkq$h5t$2...@neptunium.btinternet.com>
article
NNTP: 09:20:04 [tx] ARTICLE 52880
NNTP: 09:20:05 [rx] 220 52880 <9c0rkr$h5t$3...@neptunium.btinternet.com>
article
NNTP: 09:20:05 [tx] ARTICLE 52881
NNTP: 09:20:05 [rx] 220 52881 <9c0rks$h5t$4...@neptunium.btinternet.com>
article
NNTP: 09:20:05 [tx] ARTICLE 52882
NNTP: 09:20:05 [rx] 220 52882 <9c0rks$h5t$5...@neptunium.btinternet.com>
article
NNTP: 09:20:05 [tx] ARTICLE 52883
NNTP: 09:20:05 [rx] 220 52883 <9c0rkt$h5t$6...@neptunium.btinternet.com>
article
NNTP: 09:20:05 [db] Connection to 'news.btinternet.com' closed.
----
Robert Aldwinckle
AFAICS you could see the same error using this server too. And
according to the document you found it would be a bug in the client.
Unfortunately, it looks as if the test you did wasn't comprehensive
enough to prove that because the order you added your test messages
avoided some important test cases. (I'm assuming that you did your two
watched thread additions first.)
The point is that so far we have seen the XOVER always start from where
the XHDR left off and not from where the XHDR started. (Excerpt
included below.) If this is true generally, it can miss *new* messages
added between the time that you last synchronized and before the
messages that were inserted in your watched threads. It may also miss
messages for unwatched threads which were added between watched
messages. Hence the only new message headers we would expect to see as
a result of the XOVER would be ones for unwatched threads done after the
last message in any watched thread. The extreme case of that is that if
the last message added was for a watched thread an XOVER might not even
be issued!
Therefore, the most important test is to make sure you add messages to
unwatched threads before you add them to watched threads. We will
expect those messages to be lost. Then, I think, the simplest thing to
do will be to alternate inserting messages into watched and unwatched
threads. We will expect all unwatched messages before the last watched
message also to be lost (as demonstrated by where the XOVER starts).
(It all seems rather incredible but we have to start somewhere.) (I
wonder if you can get them back if you synchronize using "All messages"
or "Headers Only?)
You have me intrigued. I may be trying this myself too. However,
rather than creating a new identity I think that I may simply try
creating a couple of new accounts with the msnews server. Also, if
the XOVER hypothesis is wrong (e.g. it still is used the way the logs
show but there appear to be no lost messages), as a last resort we can
use a Telnet connection to simulate the same command sequence and get
*all* the trace data, not just OE's synopsis of it.
Good luck
Robert
---
"Paul" <pau...@btinternet.com> wrote in message
news:Om2gQU5yAHA.1360@tkmsftngp05...
> I've repeated a similar procedure on 'news.microsoft.com'.
> Two OE identies were synchronised so they contained the same
> recent messages. One OE identity set with two threads 'watched'
> - and the second OE identity with no threads watched.
>
> 'News log' was enabled and both OE identities were synchronised the
> same way as before ( 'New messages only'). BTW, I click on the news
> server name in the 'Folder' pane over on the left and use the
> 'Synchronize Account' button - and then swap identity for the second
> synch.
>
> Eight new messages downloaded into both the 'watched' and 'unwatched'
> OE identities. Of the eight messages, one message went into each of
> the two 'watched' threads (I'm not sure I like being this
> definite<G>). The logs are pasted below.
>
>
> A Google search for XHDR found this page titled
> "NNTP-Ext 2.6 XHDR"-
> http://www.mibsoftware.com/userkt/nntpext/0023.htm
...
NNTP: 23:26:05 [tx] XHDR References 131687-131694
NNTP: 23:26:06 [rx] 221 Xhdr information follows
NNTP: 23:26:06 [tx] XHDR Subject 131687-131694
NNTP: 23:26:06 [rx] 221 Xhdr information follows
NNTP: 23:26:06 [tx] ARTICLE 131687
NNTP: 23:26:07 [rx] 220 131687 <OOH6PD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:07 [tx] ARTICLE 131688
NNTP: 23:26:07 [rx] 220 131688 <usf8fD3yAHA.1972@tkmsftngp03>
NNTP: 23:26:07 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/22/2001 23:26:07
NNTP: 23:26:07 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 23:26:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:08 [tx] MODE READER
NNTP: 23:26:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 23:26:08 [tx] GROUP
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:08 [rx] 211 10284 109708 131694
microsoft.public.windows.inetexplorer.ie5.outlookexpress
NNTP: 23:26:08 [tx] XOVER 131689-131694
...
Paul
unwatched threads first then adding to watched threads'.
NG used news:microsoft.public.jp.test
Eight new messages creating eight threads with self explanatory
subjects were posted, i.e.
Test 8
Test 7 Watched
Test 6 Watched
Test 5
Test 4 Watched
Test 3
Test 2 Watched
Test 1
I Switched to the 'Watch' OE identity and 'Synchronized Account', 'New
messages only'. The eight test messages downloaded. Did File >
Offline and set 'Watch' as indicated by the subject lines. Then did
'Mark all read' and enabled news log
Back in the other OE identity, posted four new messgaes
into the unwatched threads - followed by four new messages into the
watched threads
Switched back to the 'Watch' identity and 'Synchronized Account',
'New massages only'.
Only four new messages downloaded from the watched threads, i.e. -
Re: Test 7 Watched
Re: Test 6 Watched
Re: Test 4 Watched
Re: Test 2 Watched
The new messages in unwatched threads didn't download.
I was suprised by this. On news.btinternet.com, in NG's with watched
threads, there was usually an unread count that would not clear doing
'Mark all read' or CTRL+SHIFT+A. This was the hint that perhaps
there were missing messages. This didn't occur on news.microsoft.com
The unread count was displayed in 'Synchronization of Newsgroups on
news.btinternet.com' and also (I think) displayed in the folder pane
e.g. [72] against the NG name. I haven't been looking for unread
counts the last day or two. I'll try and check to confirm that
BTinternet does show unread counts for messages not in OE but on the
server.
Cheers, ....Paul
***News log, new messages to unwatched threads then watched threads***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 12:03:11
NNTP: 12:03:11 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 12:03:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:12 [tx] MODE READER
NNTP: 12:03:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:12 [tx] GROUP microsoft.public.jp.test
NNTP: 12:03:13 [rx] 211 1071 3 1238 microsoft.public.jp.test
NNTP: 12:03:13 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 12:03:13
NNTP: 12:03:13 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 12:03:13 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:13 [tx] MODE READER
NNTP: 12:03:13 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:13 [tx] GROUP microsoft.public.jp.test
NNTP: 12:03:14 [rx] 211 799 2 1238 microsoft.public.jp.test
NNTP: 12:03:14 [tx] XHDR References 1231-1238
NNTP: 12:03:14 [rx] 221 Xhdr information follows
NNTP: 12:03:14 [tx] XHDR Subject 1231-1238
NNTP: 12:03:14 [rx] 221 Xhdr information follows
NNTP: 12:03:14 [tx] ARTICLE 1235
NNTP: 12:03:15 [rx] 220 1235 <#zvTTbLzAHA.160@tkmsftngp03>
NNTP: 12:03:15 [tx] ARTICLE 1236
NNTP: 12:03:15 [rx] 220 1236 <eqs1TbLzAHA.160@tkmsftngp03>
NNTP: 12:03:15 [tx] ARTICLE 1237
NNTP: 12:03:15 [rx] 220 1237 <O5EXUbLzAHA.160@tkmsftngp03>
NNTP: 12:03:15 [tx] ARTICLE 1238
NNTP: 12:03:16 [rx] 220 1238 <#LE5UbLzAHA.160@tkmsftngp03>
NNTP: 12:03:16 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 12:03:16
NNTP: 12:03:16 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 12:03:17 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:17 [tx] MODE READER
NNTP: 12:03:17 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 12:03:17 [tx] GROUP microsoft.public.jp.test
NNTP: 12:03:17 [rx] 211 491 332 1238 microsoft.public.jp.test
NNTP: 12:03:17 [db] Connection to 'news.microsoft.com' closed.
----
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:uf4tz5HzAHA.592@tkmsftngp02...
<snipped>
> Therefore, the most important test is to make sure you add messages
to
> unwatched threads before you add them to watched threads. We will
> expect those messages to be lost
<snipped>
Paul
news:microsoft.public.jp.test (with a few false starts) in much the
same way as before
Posted eight new messages, creating eight new threads -
test 40
test 39 watched
test 38
test 37 watched
test 36
test 35 watched
test 34
test 33 watched
Posted new messages -
8th to 'test 38'
7th to 'test 33 watched'
6th to 'test 36'
5th to 'test 39 watched'
4th to 'test 40'
3rd to 'test 37 watched'
2nd to 'test 34'
1st to 'test 35 watched'
So the last message posted was the 8th, into unwatched thread 'test
38' - and the first went into the thread 'test 35 watched'.
Did 'Synchronize Account, New messages only', result -
Five new messages downloaded!
I haven't tried getting the missing messages using 'Synchronize All'
and 'Headers only' yet.
Awhile ago, (I think) I've seen the 'missing' new headers download
while online in a NG after removing 'watch' from the threads - I
was just messing around at the time with the problem
Cheers again, ...Paul
**News log, alternate new messages into watched then unwatched**
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 15:50:21
NNTP: 15:50:21 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 15:50:22 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:22 [tx] MODE READER
NNTP: 15:50:22 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:22 [tx] GROUP microsoft.public.jp.test
NNTP: 15:50:22 [rx] 211 866 2 1306 microsoft.public.jp.test
NNTP: 15:50:22 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 15:50:22
NNTP: 15:50:22 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 15:50:23 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:23 [tx] MODE READER
NNTP: 15:50:23 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:23 [tx] GROUP microsoft.public.jp.test
NNTP: 15:50:23 [rx] 211 559 332 1306 microsoft.public.jp.test
NNTP: 15:50:23 [tx] XHDR References 1299-1306
NNTP: 15:50:24 [rx] 221 Xhdr information follows
NNTP: 15:50:24 [tx] XHDR Subject 1299-1306
NNTP: 15:50:24 [rx] 221 Xhdr information follows
NNTP: 15:50:24 [tx] ARTICLE 1299
NNTP: 15:50:25 [rx] 220 1299 <u6cTObNzAHA.1832@tkmsftngp05>
NNTP: 15:50:25 [tx] ARTICLE 1301
NNTP: 15:50:25 [rx] 220 1301 <OPKcPbNzAHA.1984@tkmsftngp05>
NNTP: 15:50:25 [tx] ARTICLE 1303
NNTP: 15:50:25 [rx] 220 1303 <OMgiQbNzAHA.1984@tkmsftngp05>
NNTP: 15:50:25 [tx] ARTICLE 1305
NNTP: 15:50:26 [rx] 220 1305 <eVcmRbNzAHA.1984@tkmsftngp05>
NNTP: 15:50:26 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/24/2001 15:50:26
NNTP: 15:50:26 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 15:50:26 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:26 [tx] MODE READER
NNTP: 15:50:27 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 15:50:27 [tx] GROUP microsoft.public.jp.test
NNTP: 15:50:27 [rx] 211 866 2 1306 microsoft.public.jp.test
NNTP: 15:50:27 [tx] XOVER 1306-1306
NNTP: 15:50:27 [rx] 224 Overview information follows
NNTP: 15:50:27 [tx] ARTICLE 1306
NNTP: 15:50:28 [rx] 220 1306 <OobISbNzAHA.1984@tkmsftngp05>
NNTP: 15:50:28 [db] Connection to 'news.microsoft.com' closed.
----
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:uf4tz5HzAHA.592@tkmsftngp02...
<snipped>
> Then, I think, the simplest thing to
> do will be to alternate inserting messages into watched and
unwatched
> threads. We will expect all unwatched messages before the last
watched
> message also to be lost (as demonstrated by where the XOVER starts).
> (I
> wonder if you can get them back if you synchronize using "All
messages"
> or "Headers Only?)
<snipped>
Robert Aldwinckle
"Paul" <pau...@btinternet.com> wrote in message
news:#FsSf#PzAHA.1432@tkmsftngp03
...
> Back in the other OE identity, posted four new messgaes
> into the unwatched threads - followed by four new messages into the
> watched threads
>
> Switched back to the 'Watch' identity and 'Synchronized Account',
> 'New massages only'.
>
> Only four new messages downloaded from the watched threads, i.e. -
>
> Re: Test 7 Watched
> Re: Test 6 Watched
> Re: Test 4 Watched
> Re: Test 2 Watched
>
> The new messages in unwatched threads didn't download.
...
You have just proved my conjecture too: "The extreme case of that is
that if
the last message added was for a watched thread an XOVER might not even
be issued!" The bug is that an XOVER should have been issued *at
least* for 1231-1234. The only time they can get away with not
issuing an XOVER here is when the total number of watched messages read
equals the total number of messages possible; otherwise unwatched
headers will be lost.
Robert
---
Robert Aldwinckle
"Paul" <pau...@btinternet.com> wrote in message
news:evgEdEQzAHA.2184@tkmsftngp02...
> This is 'Alternate new messages into watched then unwatched' on
> news:microsoft.public.jp.test (with a few false starts) in much the
> same way as before
...
> So the last message posted was the 8th, into unwatched thread 'test
> 38' - and the first went into the thread 'test 35 watched'.
>
> Did 'Synchronize Account, New messages only', result -
>
> Five new messages downloaded!
...
In this case you have proved the prediction "We will expect all
unwatched messages before the last watched message also to be lost (as
demonstrated by where the XOVER starts)." The XOVER should always be
issued even if you are using "Headers Only" as a Synchronization
Setting. Because you are using /New Messages Only/ the body of the
last article was downloaded as well. What should have happened is that
an XOVER be done on the entire range and *all* the remaining articles
downloaded.
That prompts the question that if they know that you want /New Messages/
why are they doing this XHDR thing at all? Except that priority is
given to watched messages I think the feature may only be useful for
/Headers Only/ users--assuming that watched messages are still
downloaded in that case.
I am *so* glad that I use /All Messages/ and that it works! The benefit
that I have found with /All Messages/ (which I have reported before) is
that it fills in the holes and by that I mean it downloads bodies for
old headers which dribble in while I have a newsgroup open while online.
Therefore, a possible implementation of /All Messages/ is that an
automated application of Tools / Mark for Offline / "Download All
Messages Later" may be done before each synchronization. However,
unless they also keep track of the sequence numbers and note which ones
aren't accounted for I can not imagine there is a way to go back and add
missing headers; you would need to do a Reset to do that.
Robert
---
Paul
the missing/hidden messages (I didn't try 'Headers only')
It seems XOVER fetched from the first XHDR reference, although I can't
really follow the log other than roughly
This is an extract from the log during 'Synchronize Account' 'New
messages only' -
NNTP: 11:30:12 [tx] GROUP microsoft.public.jp.test
NNTP: 11:30:12 [rx] 211 569 332 1329 microsoft.public.jp.test
NNTP: 11:30:12 [tx] XHDR References 1324-1329
NNTP: 11:30:12 [rx] 221 Xhdr information follows
NNTP: 11:30:12 [tx] XHDR Subject 1324-1329
NNTP: 11:30:13 [rx] 221 Xhdr information follows
NNTP: 11:30:13 [tx] ARTICLE 1327
NNTP: 11:30:13 [rx] 220 1327 <e0D9xtXzAHA.592@tkmsftngp02>
NNTP: 11:30:13 [tx] ARTICLE 1328
NNTP: 11:30:13 [rx] 220 1328 <#unfytXzAHA.592@tkmsftngp02>
NNTP: 11:30:13 [tx] ARTICLE 1329
NNTP: 11:30:14 [rx] 220 1329 <OVXDztXzAHA.592@tkmsftngp02>
NNTP: 11:30:14 [db] Connection to 'news.microsoft.com' closed.
This is an extract from the same log during 'Synchronize Account''All
messages' -
NNTP: 11:34:16 [tx] GROUP microsoft.public.jp.test
NNTP: 11:34:16 [rx] 211 1161 3 1329 microsoft.public.jp.test
NNTP: 11:34:16 [tx] XOVER 1324-1326
NNTP: 11:34:17 [rx] 224 Overview information follows
NNTP: 11:34:17 [tx] ARTICLE 1309
NNTP: 11:34:17 [rx] 220 1309 <#kVqMlRzAHA.1932@tkmsftngp05>
NNTP: 11:34:17 [tx] ARTICLE 1311
NNTP: 11:34:18 [rx] 220 1311 <uIl$KoUzAHA.2164@tkmsftngp02>
NNTP: 11:34:18 [tx] ARTICLE 1312
NNTP: 11:34:18 [rx] 220 1312 <#PLcSSWzAHA.1456@tkmsftngp02>
NNTP: 11:34:18 [tx] ARTICLE 1314
NNTP: 11:34:18 [rx] 220 1314 <eWqOEUWzAHA.1808@tkmsftngp05>
NNTP: 11:34:18 [tx] ARTICLE 1315
NNTP: 11:34:19 [rx] 220 1315 <e4V3sYWzAHA.2324@tkmsftngp02>
NNTP: 11:34:19 [tx] ARTICLE 1316
NNTP: 11:34:19 [rx] 220 1316 <#uSZtYWzAHA.2324@tkmsftngp02>
NNTP: 11:34:19 [tx] ARTICLE 1324
NNTP: 11:34:20 [rx] 220 1324 <e#APsrXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [tx] ARTICLE 1325
NNTP: 11:34:20 [rx] 220 1325 <OI92srXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [tx] ARTICLE 1326
NNTP: 11:34:20 [rx] 220 1326 <#WVYtrXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [db] Connection to 'news.microsoft.com' closed.
This was using the 'Adding to unwatched threads first then adding to
watched threads' scheme - using six threads, three new messages to
unwatched then three new messgaes to watched
Cheers, ...Paul
----
> "Robert Aldwinckle" <rob...@techemail.com> wrote in message
> news:uf4tz5HzAHA.592@tkmsftngp02...
<snipped>
> We will expect all unwatched messages before the last
> watched message also to be lost (as demonstrated by where the
> XOVER starts).
> (I wonder if you can get them back if you synchronize using
> "All messages" or "Headers Only?)
<snipped>
Paul
news server, appear as an unread count next to the NG name in
the folder pane over on the left e.g. alt.awelch.test [2]
This is after 'Mark all read'.
Edit > 'Mark all read' is then greyed out
The unread count also appears in 'Synchronisation of Newsgroups on
news.btinternet.com'
Catch-up clears the unread count to nil
Looking at the log -
NNTP: 16:03:44 [rx] 211 28 649 676 alt.awelch.test
NNTP: 16:03:44 [tx] XHDR References 671-676
NNTP: 16:03:44 [rx] 221 References fields follow
NNTP: 16:03:44 [tx] XHDR Subject 671-676
NNTP: 16:03:44 [rx] 221 Subject fields follow
<snip>
NNTP: 16:03:46 [tx] GROUP alt.awelch.test
NNTP: 16:03:46 [rx] 211 28 649 676 alt.awelch.test
NNTP: 16:03:46 [tx] XOVER 676-676
NNTP: 16:03:46 [rx] 224 data follows
NNTP: 16:03:46 [tx] ARTICLE 676
With XOVER starting on the last or after the XHDR references - this
seems the usual 'funny' so I guess this is just the way
news.btinternet.com. handles things
Your hypothesis looks good. I won't send any more messages unless its
really obvious I should.
BTW, avoiding 'Synchronize Account' does seem the workaround, no
problems now with the usual NG list
Cheers again, ...Paul
"Paul" <pau...@btinternet.com> wrote in message
news:#FsSf#PzAHA.1432@tkmsftngp03...
<Snipped; about messages not downloading from msnews>
> The new messages in unwatched threads didn't download.
>
> I was suprised by this. On news.btinternet.com, in NG's with
> watched threads, there was usually an unread count that would
> not clear doing 'Mark all read' or CTRL+SHIFT+A. This was
> the hint that perhaps there were missing messages. This didn't
> occur on news.microsoft.com
<snipped>
Paul
> I love it when predictions work...
<big grin> ...thanks again, ...Paul
Paul
> Hi Robert - I've tried your suggestion 'Synchronise All'.
> Previously, I'd been using 'Synchronize Account'.
>
> Using 'Synchronise All' combined with 'New messages only' seems
> to avoid the problem. Can't quite believe it :)
Ugh.
Where I wrote 'Synchronise All' that's from the OE menu -
Tools > 'Synchronize All'
This appears to download all messages from all news accounts within an
OE identity (two news accounts in my case)
I guess the menu command ' Synchronize All' overides any settings in
'Synchronization of Newsgroups on news...' so my reference to
'New messages only' doesn't make much sense.
I guess Tools > 'Synchronize All' is the equivalent of 'Synchronize
Account' with all NG's set to 'All messages' - if there's only one
news account in the OE identity
Not sure I've got this interaction crystal clear, another month or
two might figure it :) ...Paul
Paul
<About 'Synchronize All', Synchronize Account' and 'Synchronization
Settings eg 'New messages only' and 'All messages'>
Synchronizing from a NG with messages posted using the 'Alternate new
messages to watched then unwatched' scheme, using different
synchronization settings -
1) 'New messages only' set in ' Synchronization of newgroups on
news.microsoft.com' and 'Synchronize All' from the Tools menu
does no XHDR and a successful XOVER
All new messages download
2) 'All messages only' set in ' Synchronization of newgroups on
news.microsoft.com' and 'Synchronize All' from the Tools menu
does XHDR and successful, multiple XOVER
All new messages download
3) 'New messages only' and clicking 'Synchronize Account' button in '
Synchronization of newgroups on news.microsoft.com'
does XHDR and a faulty XOVER leaving messages on the news server
Not all new messages downloaded
4) 'All messages' and clicking 'Synchronize Account' button in '
Synchronization of newgroups on news.microsoft.com'
does XHDR and successful, multiple XOVER
Log from 4)...
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/26/2001 10:22:11
NNTP: 10:22:11 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 10:22:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 10:22:12 [tx] MODE READER
NNTP: 10:22:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 10:22:12 [tx] GROUP microsoft.public.jp.test
NNTP: 10:22:12 [rx] 211 604 332 1366 microsoft.public.jp.test
NNTP: 10:22:12 [tx] XHDR References 1361-1366
NNTP: 10:22:13 [rx] 221 Xhdr information follows
NNTP: 10:22:13 [tx] XHDR Subject 1361-1366
NNTP: 10:22:13 [rx] 221 Xhdr information follows
NNTP: 10:22:13 [tx] ARTICLE 1361
NNTP: 10:22:13 [rx] 220 1361 <OKMZqpjzAHA.1908@tkmsftngp03>
NNTP: 10:22:13 [tx] ARTICLE 1363
NNTP: 10:22:14 [rx] 220 1363 <eSTkrpjzAHA.1908@tkmsftngp03>
NNTP: 10:22:14 [tx] ARTICLE 1365
NNTP: 10:22:14 [rx] 220 1365 <e#XvspjzAHA.1908@tkmsftngp03>
NNTP: 10:22:14 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/26/2001 10:22:14
NNTP: 10:22:14 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 10:22:15 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 10:22:15 [tx] MODE READER
NNTP: 10:22:15 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 10:22:15 [tx] GROUP microsoft.public.jp.test
NNTP: 10:22:15 [rx] 211 924 2 1366 microsoft.public.jp.test
NNTP: 10:22:15 [tx] XOVER 1366-1366
NNTP: 10:22:16 [rx] 224 Overview information follows
NNTP: 10:22:16 [tx] XOVER 1364-1364
NNTP: 10:22:16 [rx] 224 Overview information follows
NNTP: 10:22:16 [tx] XOVER 1362-1362
NNTP: 10:22:16 [rx] 224 Overview information follows
NNTP: 10:22:16 [tx] XOVER 1358-1358
NNTP: 10:22:17 [rx] 224 Overview information follows
NNTP: 10:22:17 [tx] XOVER 1356-1356
NNTP: 10:22:17 [rx] 224 Overview information follows
NNTP: 10:22:17 [tx] XOVER 1354-1354
NNTP: 10:22:17 [rx] 224 Overview information follows
NNTP: 10:22:17 [tx] ARTICLE 1354
NNTP: 10:22:18 [rx] 220 1354 <u56DUbjzAHA.1392@tkmsftngp02>
NNTP: 10:22:18 [tx] ARTICLE 1356
NNTP: 10:22:18 [rx] 220 1356 <#$q77djzAHA.1396@tkmsftngp05>
NNTP: 10:22:18 [tx] ARTICLE 1358
NNTP: 10:22:18 [rx] 220 1358 <#8AC9djzAHA.1396@tkmsftngp05>
NNTP: 10:22:18 [tx] ARTICLE 1362
NNTP: 10:22:19 [rx] 220 1362 <Ogu#qpjzAHA.1908@tkmsftngp03>
NNTP: 10:22:19 [tx] ARTICLE 1364
NNTP: 10:22:19 [rx] 220 1364 <OUBLspjzAHA.1908@tkmsftngp03>
NNTP: 10:22:19 [tx] ARTICLE 1366
NNTP: 10:22:20 [rx] 220 1366 <usVUtpjzAHA.1908@tkmsftngp03>
NNTP: 10:22:20 [db] Connection to 'news.microsoft.com' closed.
I've only done this once and it's getting complex, I think it's an
accurate representation, although the scope for messing up is
increasing .
Looks a bit suprising. I can post a full log.
I'm happy to leave it at this, unless there's something
obviously wrong with my notes that's not apparent to me :) ...Paul
Robert Aldwinckle
it keeps track of two synchronization checkpoints, one which says where
you started this session and one which says where your latest /New
Messages Only/ update has brought you. Fortunately, when you switched
to /All Messages/ it reverted back to the first checkpoint. Again, this
only really makes sense for the /Headers Only/ case. Downloading bodies
in the same range that should have been done for the /New Messages Only/
case would normally be redundant as is redoing an XOVER again for both
cases.
Notice how it is also "filling in the holes" as I described in my last
post? This answers the question I had about implementation (i.e., how
the holes are filled in). Evidently they just get bodies for the
headers they know about and *don't* doublecheck for missing headers in
the range. That means that if you don't recover missing headers _now_
(this session) the way you have done they are gone until you do a
complete Reset.
(!) Or maybe not? What if you were only getting so many messages at a
time: You might be able to go back and get some more which would reset
the synchronization counter to a lower number so then a new
synchronization with /All Messages/ would pick up the ones you were
missing in the range you had downloaded already. Again this will depend
on implementation. If the implementation tries to avoid an assumed
redundancy you will still be out of luck.
There's one small mystery I'm curious about which may be answered in
some of the intervening stuff you snipped. What happened to make the
server change its GROUP response so dramatically? I.e., from
> NNTP: 11:30:12 [rx] 211 569 332 1329 microsoft.public.jp.test
to
> NNTP: 11:34:16 [rx] 211 1161 3 1329 microsoft.public.jp.test
I hope I haven't misinterpreted what you're implying when you say "same
log". I'm assuming you also mean same session; otherwise the
inferences I have been making will be invalid.
Robert
---
"Paul" <pau...@btinternet.com> wrote in message
news:#2IQzfbzAHA.1344@tkmsftngp03...
Paul
About filling in the holes -
Because of the 'missing messages' problem, I wasn't
confident/mis-understood the action of the synchronization settings
slightly. Using 'all messages' makes sense and I recognize the problem
of headers sneaking in while online in a NG
My first test message was article number 1318. Looking at article number
1315 from the XOVER, 1315 is buried away in a long thread. It would have
downloaded as a header when I first went online in the NG - before any
testing. It was waiting for an 'All messages' (!) (Always assumming
I'm reading the logs and headers correctly)
About the small mystery between -
NNTP: 11:30:12 [rx] 211 569 332 1329 microsoft.public.jp.test
to
NNTP: 11:34:16 [rx] 211 1161 3 1329 microsoft.public.jp.test
Briefly, the log was running continuously between these times; think I
set OE offline, did a 'mark all read' and changed the synch. settings,
set OE back online - for the final synchronization. The unedited log is
below marked [1]
In more detail -
Six messages were posted -
Test 46 (article number 1323)
Test 45 Watched (article number 1322)
Test 44 Watched (article number 1321)
Test 43 (article number 1320)
Test 42 Watched (article number 1319)
Test 41 (article number 1318)
These were downloaded in the 'watch' OE identity, OE set to offline,
'watch' set on the watched threads, did 'mark all read' and news log
enabled
After the new messages were posted (from another OE identity), did
'synchronize account' 'new messages only'.
Then set OE offline and did (from memory but fairly certain) 'mark
all read', then set the new synchronization setting.
Set OE back online and did 'synchronize account' 'all messages'. Set OE
to work offline, disabled 'news log'.
Cheers again, ...Paul
[1]
***News log, six threads, posting new messages to unwatched threads
then watched threads, followed by Synchronize Account, New Messages
Only, then Synchronize Account, All Messages***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:30:10
NNTP: 11:30:10 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:30:10 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:10 [tx] MODE READER
NNTP: 11:30:11 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:11 [tx] GROUP microsoft.public.jp.test
NNTP: 11:30:11 [rx] 211 569 332 1329 microsoft.public.jp.test
NNTP: 11:30:11 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:30:11
NNTP: 11:30:11 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:30:11 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:11 [tx] MODE READER
NNTP: 11:30:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:12 [tx] GROUP microsoft.public.jp.test
NNTP: 11:30:12 [rx] 211 569 332 1329 microsoft.public.jp.test
NNTP: 11:30:12 [tx] XHDR References 1324-1329
NNTP: 11:30:12 [rx] 221 Xhdr information follows
NNTP: 11:30:12 [tx] XHDR Subject 1324-1329
NNTP: 11:30:13 [rx] 221 Xhdr information follows
NNTP: 11:30:13 [tx] ARTICLE 1327
NNTP: 11:30:13 [rx] 220 1327 <e0D9xtXzAHA.592@tkmsftngp02>
NNTP: 11:30:13 [tx] ARTICLE 1328
NNTP: 11:30:13 [rx] 220 1328 <#unfytXzAHA.592@tkmsftngp02>
NNTP: 11:30:13 [tx] ARTICLE 1329
NNTP: 11:30:14 [rx] 220 1329 <OVXDztXzAHA.592@tkmsftngp02>
NNTP: 11:30:14 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:30:14
NNTP: 11:30:14 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:30:14 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:14 [tx] MODE READER
NNTP: 11:30:15 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:30:15 [tx] GROUP microsoft.public.jp.test
NNTP: 11:30:15 [rx] 211 889 2 1329 microsoft.public.jp.test
NNTP: 11:30:15 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:34:13
NNTP: 11:34:13 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:34:14 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:14 [tx] MODE READER
NNTP: 11:34:14 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:14 [tx] GROUP microsoft.public.jp.test
NNTP: 11:34:14 [rx] 211 569 332 1329 microsoft.public.jp.test
NNTP: 11:34:14 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:34:14
NNTP: 11:34:14 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:34:15 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:15 [tx] MODE READER
NNTP: 11:34:15 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:15 [tx] GROUP microsoft.public.jp.test
NNTP: 11:34:15 [rx] 211 569 332 1329 microsoft.public.jp.test
NNTP: 11:34:15 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/25/2001 11:34:15
NNTP: 11:34:15 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 11:34:16 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:16 [tx] MODE READER
NNTP: 11:34:16 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 11:34:16 [tx] GROUP microsoft.public.jp.test
NNTP: 11:34:16 [rx] 211 1161 3 1329 microsoft.public.jp.test
NNTP: 11:34:16 [tx] XOVER 1324-1326
NNTP: 11:34:17 [rx] 224 Overview information follows
NNTP: 11:34:17 [tx] ARTICLE 1309
NNTP: 11:34:17 [rx] 220 1309 <#kVqMlRzAHA.1932@tkmsftngp05>
NNTP: 11:34:17 [tx] ARTICLE 1311
NNTP: 11:34:18 [rx] 220 1311 <uIl$KoUzAHA.2164@tkmsftngp02>
NNTP: 11:34:18 [tx] ARTICLE 1312
NNTP: 11:34:18 [rx] 220 1312 <#PLcSSWzAHA.1456@tkmsftngp02>
NNTP: 11:34:18 [tx] ARTICLE 1314
NNTP: 11:34:18 [rx] 220 1314 <eWqOEUWzAHA.1808@tkmsftngp05>
NNTP: 11:34:18 [tx] ARTICLE 1315
NNTP: 11:34:19 [rx] 220 1315 <e4V3sYWzAHA.2324@tkmsftngp02>
NNTP: 11:34:19 [tx] ARTICLE 1316
NNTP: 11:34:19 [rx] 220 1316 <#uSZtYWzAHA.2324@tkmsftngp02>
NNTP: 11:34:19 [tx] ARTICLE 1324
NNTP: 11:34:20 [rx] 220 1324 <e#APsrXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [tx] ARTICLE 1325
NNTP: 11:34:20 [rx] 220 1325 <OI92srXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [tx] ARTICLE 1326
NNTP: 11:34:20 [rx] 220 1326 <#WVYtrXzAHA.1392@tkmsftngp02>
NNTP: 11:34:20 [db] Connection to 'news.microsoft.com' closed.
----
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:ekrNCqrzAHA.1456@tkmsftngp02...
Paul
I've repeated the test doing -
'Synchronize account' 'new messages only'
Doing nothing other than swap identity and changing the synch. setting.
'Synchronize account' 'all messages'
An extract here -
NNTP: 22:34:44 [tx] GROUP microsoft.public.jp.test
NNTP: 22:34:44 [rx] 211 1215 3 1388 microsoft.public.jp.test
and
NNTP: 22:35:46 [tx] GROUP microsoft.public.jp.test
NNTP: 22:35:46 [rx] 211 1215 3 1388 microsoft.public.jp.test
I've also repeated the test, doing -
'Synchronize account' 'new messages only'
Setting OE offline, doing 'mark all read', setting OE online
'Synchronize account' 'all messages'
Extract -
NNTP: 22:15:28 [tx] GROUP microsoft.public.jp.test
NNTP: 22:15:28 [rx] 211 611 332 1382 microsoft.public.jp.test
and
NNTP: 22:18:25 [tx] GROUP microsoft.public.jp.test
NNTP: 22:18:25 [rx] 211 1209 3 1382 microsoft.public.jp.test
So it's irrational behaviour between synchronizing
In both cases, during both synchronizations, looking at the Folder
View over on the left, the NG name displayed -
microsoft.public.jp.test [6] then about one second later
microsoft.public.jp.test [3]
Regards, ...Paul
PS - can post the full log(s) if necessary
Paul
looks -
New messages are not downloaded from a news server if they were
posted to the NG before a new message going into a watched thread -
AND if 'synchronize account', 'new messages only' is used to
synchronize.
The problem doesn't occur using -
'synchronize account', 'all messages'
'synchronize all', 'all messages'
'synchronize all', 'new messages only'
The problem only seems to occur when 'watch' is used on a thread
Some news servers show an unread count in OE for the messages that were
left stranded on the news server, perhaps because they run old software
or use NNRP(?)
The workaround seems; avoid using 'synchronize account, 'new messages
only' for NG's with watched threads.
I haven't had any apparent missing messages since using -
'synchronize all', 'all messages'
I'm grateful for the help given - and I'm happy to be
corrected on any of this
...Paul
"An analogue brain in a digital domain" - Enya
PS -
This is the test and news log that I'm basing the comments on -
The test was posting six new messages into watched then unwatched
threads alternatively, so the last new message went into an unwatched
thread. This was done four times and synchronized after each time
using the settings as marked within the news log -
*** 1) Synchronize All, New Messages Only ***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:36:25
NNTP: 13:36:25 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:36:26 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:36:26 [tx] MODE READER
NNTP: 13:36:26 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:36:26 [tx] GROUP microsoft.public.jp.test
NNTP: 13:36:27 [rx] 211 1293 3 1466 microsoft.public.jp.test
NNTP: 13:36:27 [tx] XOVER 1461-1466
NNTP: 13:36:27 [rx] 224 Overview information follows
NNTP: 13:36:27 [tx] ARTICLE 1461
NNTP: 13:36:28 [rx] 220 1461 <eob8Of#zAHA.428@tkmsftngp02>
NNTP: 13:36:28 [tx] ARTICLE 1462
NNTP: 13:36:28 [rx] 220 1462 <OyXkPf#zAHA.428@tkmsftngp02>
NNTP: 13:36:28 [tx] ARTICLE 1463
NNTP: 13:36:28 [rx] 220 1463 <egVJQf#zAHA.428@tkmsftngp02>
NNTP: 13:36:28 [tx] ARTICLE 1464
NNTP: 13:36:29 [rx] 220 1464 <OmqwQf#zAHA.428@tkmsftngp02>
NNTP: 13:36:29 [tx] ARTICLE 1465
NNTP: 13:36:29 [rx] 220 1465 <OA0WRf#zAHA.2288@tkmsftngp02>
NNTP: 13:36:29 [tx] ARTICLE 1466
NNTP: 13:36:29 [rx] 220 1466 <eux7Rf#zAHA.2288@tkmsftngp02>
NNTP: 13:36:29 [db] Connection to 'news.microsoft.com' closed.
*** 2) Synchronize All, All Messages ***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:44:39
NNTP: 13:44:39 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:44:40 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:44:40 [tx] MODE READER
NNTP: 13:44:40 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:44:40 [tx] GROUP microsoft.public.jp.test
NNTP: 13:44:40 [rx] 211 695 332 1472 microsoft.public.jp.test
NNTP: 13:44:41 [tx] XOVER 1467-1472
NNTP: 13:44:41 [rx] 224 Overview information follows
NNTP: 13:44:41 [tx] ARTICLE 1467
NNTP: 13:44:41 [rx] 220 1467 <ueW8bj#zAHA.1352@tkmsftngp05>
NNTP: 13:44:41 [tx] ARTICLE 1468
NNTP: 13:44:42 [rx] 220 1468 <u04hcj#zAHA.1352@tkmsftngp05>
NNTP: 13:44:42 [tx] ARTICLE 1469
NNTP: 13:44:42 [rx] 220 1469 <eH4Ddj#zAHA.1352@tkmsftngp05>
NNTP: 13:44:42 [tx] ARTICLE 1470
NNTP: 13:44:42 [rx] 220 1470 <edapdj#zAHA.1352@tkmsftngp05>
NNTP: 13:44:42 [tx] ARTICLE 1471
NNTP: 13:44:43 [rx] 220 1471 <OsyKej#zAHA.1352@tkmsftngp05>
NNTP: 13:44:43 [tx] ARTICLE 1472
NNTP: 13:44:43 [rx] 220 1472 <OOKyej#zAHA.1352@tkmsftngp05>
NNTP: 13:44:43 [db] Connection to 'news.microsoft.com' closed.
*** 3) Synchronize Account, New Messages Only***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:49:55
NNTP: 13:49:55 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:49:56 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:49:56 [tx] MODE READER
NNTP: 13:49:56 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:49:56 [tx] GROUP microsoft.public.jp.test
NNTP: 13:49:57 [rx] 211 1033 2 1478 microsoft.public.jp.test
NNTP: 13:49:57 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:49:57
NNTP: 13:49:57 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:49:57 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:49:57 [tx] MODE READER
NNTP: 13:49:58 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:49:58 [tx] GROUP microsoft.public.jp.test
NNTP: 13:49:58 [rx] 211 701 332 1478 microsoft.public.jp.test
NNTP: 13:49:58 [tx] XHDR References 1473-1478
NNTP: 13:49:58 [rx] 221 Xhdr information follows
NNTP: 13:49:58 [tx] XHDR Subject 1473-1478
NNTP: 13:49:59 [rx] 221 Xhdr information follows
NNTP: 13:49:59 [tx] ARTICLE 1473
NNTP: 13:49:59 [rx] 220 1473 <eLeYYn#zAHA.1256@tkmsftngp02>
NNTP: 13:49:59 [tx] ARTICLE 1475
NNTP: 13:49:59 [rx] 220 1475 <uUacZn#zAHA.1256@tkmsftngp02>
NNTP: 13:49:59 [tx] ARTICLE 1477
NNTP: 13:50:00 [rx] 220 1477 <uRwian#zAHA.1256@tkmsftngp02>
NNTP: 13:50:00 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:50:00
NNTP: 13:50:00 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:50:00 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:50:00 [tx] MODE READER
NNTP: 13:50:01 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:50:01 [tx] GROUP microsoft.public.jp.test
NNTP: 13:50:01 [rx] 211 1033 2 1478 microsoft.public.jp.test
NNTP: 13:50:01 [tx] XOVER 1478-1478
NNTP: 13:50:01 [rx] 224 Overview information follows
NNTP: 13:50:01 [tx] ARTICLE 1478
NNTP: 13:50:02 [rx] 220 1478 <#$tHbn#zAHA.1256@tkmsftngp02>
NNTP: 13:50:02 [db] Connection to 'news.microsoft.com' closed.
*** 4) Synchronize Account, All Messages***
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:56:07
NNTP: 13:56:07 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:56:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:08 [tx] MODE READER
NNTP: 13:56:08 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:08 [tx] GROUP microsoft.public.jp.test
NNTP: 13:56:08 [rx] 211 707 332 1484 microsoft.public.jp.test
NNTP: 13:56:08 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:56:08
NNTP: 13:56:08 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:56:09 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:09 [tx] MODE READER
NNTP: 13:56:09 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:09 [tx] GROUP microsoft.public.jp.test
NNTP: 13:56:09 [rx] 211 1311 3 1484 microsoft.public.jp.test
NNTP: 13:56:09 [tx] XHDR References 1479-1484
NNTP: 13:56:10 [rx] 221 Xhdr information follows
NNTP: 13:56:10 [tx] XHDR Subject 1479-1484
NNTP: 13:56:10 [rx] 221 Xhdr information follows
NNTP: 13:56:10 [tx] ARTICLE 1479
NNTP: 13:56:10 [rx] 220 1479 <ufxBFr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:10 [tx] ARTICLE 1481
NNTP: 13:56:11 [rx] 220 1481 <#n4MGr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:11 [tx] ARTICLE 1483
NNTP: 13:56:11 [rx] 220 1483 <eANWHr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:11 [db] Connection to 'news.microsoft.com' closed.
Microsoft Internet Messaging API 5.50.4133.2400
NNTP Log started at 04/28/2001 13:56:11
NNTP: 13:56:11 [db] Connecting to 'news.microsoft.com' on port 119.
NNTP: 13:56:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:12 [tx] MODE READER
NNTP: 13:56:12 [rx] 200 NNTP Service 5.00.0984 Version: 5.0.2195.1608
Posting Allowed
NNTP: 13:56:12 [tx] GROUP microsoft.public.jp.test
NNTP: 13:56:12 [rx] 211 1039 2 1484 microsoft.public.jp.test
NNTP: 13:56:12 [tx] XOVER 1484-1484
NNTP: 13:56:13 [rx] 224 Overview information follows
NNTP: 13:56:13 [tx] XOVER 1482-1482
NNTP: 13:56:13 [rx] 224 Overview information follows
NNTP: 13:56:13 [tx] XOVER 1480-1480
NNTP: 13:56:13 [rx] 224 Overview information follows
NNTP: 13:56:13 [tx] XOVER 1476-1476
NNTP: 13:56:14 [rx] 224 Overview information follows
NNTP: 13:56:14 [tx] XOVER 1474-1474
NNTP: 13:56:14 [rx] 224 Overview information follows
NNTP: 13:56:14 [tx] ARTICLE 1474
NNTP: 13:56:15 [rx] 220 1474 <#FC7Yn#zAHA.1256@tkmsftngp02>
NNTP: 13:56:15 [tx] ARTICLE 1476
NNTP: 13:56:15 [rx] 220 1476 <erA$Zn#zAHA.1256@tkmsftngp02>
NNTP: 13:56:15 [tx] ARTICLE 1480
NNTP: 13:56:15 [rx] 220 1480 <u56nFr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:15 [tx] ARTICLE 1482
NNTP: 13:56:16 [rx] 220 1482 <OW2xGr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:16 [tx] ARTICLE 1484
NNTP: 13:56:16 [rx] 220 1484 <eaW8Hr#zAHA.2088@tkmsftngp03>
NNTP: 13:56:16 [db] Connection to 'news.microsoft.com' closed.
----
"Paul" <pau...@btinternet.com> wrote in message
news:#qkKQakzAHA.2164@tkmsftngp02...
"Paul" <pau...@btinternet.com> wrote in message
news:O95N15dzAHA.1768@tkmsftngp02...
> "Paul" <pau...@btinternet.com> wrote in message
> news:eXmDfU$yAHA.720@tkmsftngp03...
<About 'Synchronize All', Synchronize Account' and 'Synchronization
Settings eg 'New messages only' and 'All messages'>
Synchronizing from a NG with messages posted using the 'Alternate new
messages to watched then unwatched' scheme, using different
synchronization settings -
1) 'New messages only' set in ' Synchronization of newgroups on
news.microsoft.com' and 'Synchronize All' from the Tools menu
does no XHDR and a successful XOVER
All new messages download
2) 'All messages only' set in ' Synchronization of newgroups on
news.microsoft.com' and 'Synchronize All' from the Tools menu
does XHDR and successful, multiple XOVER
All new messages download
***comment: 2) now looks an error on my part and should be 'does no XHDR
and succesful XOVER'***
3) 'New messages only' and clicking 'Synchronize Account' button in '
Synchronization of newgroups on news.microsoft.com'
does XHDR and a faulty XOVER leaving messages on the news server
Not all new messages downloaded
4) 'All messages' and clicking 'Synchronize Account' button in '
Synchronization of newgroups on news.microsoft.com'
does XHDR and successful, multiple XOVER
***comment: it was apparent from the snipped log - all new messages were
downloaded plus the stranded messages from 4)***
Log from 4)...
<snipped>