In news.software.readers, Lafe <
la...@lafes.newlafe.net> wrote:
> On 2021-08-26, Tavis Ormandy <
tav...@gmail.com> wrote:
>> Hmm, maybe try `set prefer_head 2`? If that fixes it, seems like it is
>> your provider (Note that scoring will be much slower without overviews,
>> but maybe that doesn't bother you!).
> Thanks for the suggestion! Setting it to prefer_head did fix it, so I
> agree that seems to point to an issue with my nntp server. It changed
> to the behavior I see with "Newsgroups:" rules, where it wants to
> download all of the articles to perform the scoring.
Have you tried to look at the overview records yourself?
Path: [...]
+ feed.usenet.farm!feed.usenet.farm!
tr2.eu1.usenetexpress.com!feeder.
+
usenetexpress.com!
tr1.iad1.usenetexpress.com!
+ 2a07:8080:119:fe:f19b:d5b2:4545:7979.MISMATCH!
news.newsdemon.com!not-
+ for-mail
Newsdemon seems to be using IPv6 without IPv6 reverse names.
Anyway, general method is:
telnet
news.newsdemon.com 119
AUTHINFO USER username
AUTHINFO PASS password
LIST overview.fmt
XOVER group.name:articlenum
QUIT
AUTHINFO only used if needed, there's also an "AUTHINFO GENERIC ..."
variation. The overview.fmt file gives the details of what to expect.
The local one here is:
Subject:
From:
Date:
Message-ID:
References:
Bytes:
Lines:
Xref:full
NNTP-Posting-Host:full
That gives the meaning of each line in the output, and the ones marked
"full" will have a header name in front of them, the overs just the
field value.
The XOVER command can get a single article or a range.
XOVER news.software.readers:1000
XOVER news.software.readers:1000-1050
I've heard of bugs in newsreaders with values after the standard
Subject: to Lines: entries that _don't_ have the header name. One
such bug is why this site has "NNTP-Posting-Host:full". I think
it was in Xnews.
> So now if I pull more than 15 or 20 articles when I enter a group,
> slrn says there's an error and "crashes" to the command line saying
> that it can't recover.
> I think this is also likely a weirdness with how it requests the
> articles and my news provider killing the connection or something.
As someone who never uses slrn, but has a vague interest in nntp
clients, I'm curious what's going on here. I looked into this thread
because I suspected some overview db issues.
Elijah
------
uses trn and perl NNTP module scripts for his news