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

[Jesper Harder <harder@myrealbox.com>]

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).