Re: 423 bad article number from local spool but header are there?

Re: 423 bad article number from local spool but header are there?

[Jesper Harder]

John Covici <covici@ccs.covici.com> writes:

> I am using Oort gnus 0.07, and I discovered in most of the usenet
> groups I subscribe to, that when I went into the summary page, the
> first several articles (or more maybe depending on the group), had the
> header info, subject, etc. but when I tried to read them I got 423 bad
> article number from the local server.  Where does it keep that header
> stuff and how can it get out of sync with the spool -- and aside from
> hitting space at each one of those and gnus marking them as g, is
> there any way to fix such a thing?

Maybe

  (setq gnus-agent nil)

will help.  Since you're reading from a local spool, there's no point in
using the agent (which was turned on by default in Oort 0.7).

Re: 423 bad article number from local spool but header are there?

[John Covici]

Looks like it did it, there was a directory under News called agent
with what looked like overview files, in addition to the ones for the
back end for mail!

Thanks.

on Sat, 30 Nov 2002 04:05:19 +0100 Jesper Harder <harder@myrealbox.com> wrote:

> John Covici <covici@ccs.covici.com> writes:
>
>> I am using Oort gnus 0.07, and I discovered in most of the usenet
>> groups I subscribe to, that when I went into the summary page, the
>> first several articles (or more maybe depending on the group), had the
>> header info, subject, etc. but when I tried to read them I got 423 bad
>> article number from the local server.  Where does it keep that header
>> stuff and how can it get out of sync with the spool -- and aside from
>> hitting space at each one of those and gnus marking them as g, is
>> there any way to fix such a thing?
>
> Maybe
>
>   (setq gnus-agent nil)
>
> will help.  Since you're reading from a local spool, there's no point in
> using the agent (which was turned on by default in Oort 0.7).

-- 
         John Covici
         covici@ccs.covici.com

Re: 423 bad article number from local spool but header are there?

[Kai Großjohann]

Jochem Huhmann <joh@gmx.net> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Jochem Huhmann <joh@gmx.net> writes:
>>
>>> Hmm. Interesting. I upgraded to Oort some time ago and didn't knew that.
>>> I did notice though that ticked articles don't disappear in the summary
>>> even when the article has expired on my local nntp-server and I can't
>>> open them anymore.
>>
>> Are they also marked with `*'?  Then they are cached.  But they
>> should be readable...
>
> No, they only have a "!" and they're not readable. Hmm, I'll disable the
> agent and enter ticked articles I'd like to keep into the cache.

You don't have to disable the agent.

> Anyway, this looks like a misfeature or at least undesired behaviour to
> me. When the agent is enabled it should either automatically download
> and store ticked articles or toss the mark when the article is expired
> on the server.

That's right.  I'm not sure if Kevin is reading this...  Want to
report it to the Gnus mailing list?
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: 423 bad article number from local spool but header are there?

[Jochem Huhmann]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>> Anyway, this looks like a misfeature or at least undesired behaviour to
>> me. When the agent is enabled it should either automatically download
>> and store ticked articles or toss the mark when the article is expired
>> on the server.
>
> That's right.  I'm not sure if Kevin is reading this...  Want to
> report it to the Gnus mailing list?

Hmm, I'm using a quite old Oort Gnus, I've never used Agent
intentionally and I'm also not on the Gnus mailing list (Gnus does not
have a gnus-report-bug). So if somebody would step in and report this I
wouldn't object ;-)


        Jochem

Re: 423 bad article number from local spool but header are there?

[Jochem Huhmann]

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

> JFTR: Oort Gnus v0.07 (see Jochem's header) doesn't have Kevin's agent
> code (dunno if this is relevant or not).

Well, I don't know too. 

>> I've never used Agent intentionally and I'm also not on the Gnus
>> mailing list
>
> When using Oort, it's recommended to read ding. The change concerning
> the agent was announced in the news file (GNUS-NEWS).

Yep, but I'm still just a Gnus user and have more than enough other
lists to follow. I tried Oort for the new pgp/gpg-support and kept it
since I had no problems with it.

>> (Gnus does not have a gnus-report-bug). 
>
> What's wrong with `M-x gnus-bug RET'? ;-)

Err... Nothing, I just looked for a function similar to report-bug ;-)
Good to know, thanks. 

Anyway, I don't have a problem reporting something that looks clearly
like a bug. But this behaviour being just a little bit unexpected with
ticked articles and the agent is something quite not so clear. I even
don't know how the agent is supposed to work since I've never needed nor
used it. I will still just file a bug report stating what I know if
nobody more current with Oort and more knowledgeable about agent will
take care.


        Jochem

Re: 423 bad article number from local spool but header are there?

[Kai Großjohann]

Jochem Huhmann <joh@gmx.net> writes:

> Hmm, I'm using a quite old Oort Gnus, I've never used Agent
> intentionally and I'm also not on the Gnus mailing list (Gnus does not
> have a gnus-report-bug). So if somebody would step in and report this I
> wouldn't object ;-)

Gnus has M-x gnus-bug RET.

But that sends the message to the wrong place anyhow.

Recent Oorts do header caching by default.  I think the native select
method was cached for quite some time now.

Hm.  0.07 is recent enough for header caching, but not recent enough
for Kevin's new code.
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)