Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: John Covici <covici@ccs.covici.com>
Subject: Re: 423 bad article number from local spool but header are there?
Date: Sat, 30 Nov 2002 07:13:33 -0500	[thread overview]
Message-ID: <m3hedztfv6.fsf@ccs.covici.com> (raw)
In-Reply-To: <m3smxjbvv4.fsf@defun.localdomain>

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


  reply	other threads:[~2002-11-30 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3d6ooxxx7.fsf@ccs.covici.com>
2002-11-30  3:05 ` Jesper Harder
2002-11-30 12:13   ` John Covici [this message]
     [not found]   ` <873cpjw7lh.fsf@nova.revier.com>
     [not found]     ` <84u1hzasf9.fsf@lucy.cs.uni-dortmund.de>
     [not found]       ` <878yz9uxdg.fsf@nova.revier.com>
2002-12-02  7:53         ` Kai Großjohann
2002-12-02 17:33           ` Jochem Huhmann
     [not found]             ` <v9isyccmoe.fsf@marauder.physik.uni-ulm.de>
2002-12-02 18:59               ` Jochem Huhmann
2002-12-02 20:12             ` Kai Großjohann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3hedztfv6.fsf@ccs.covici.com \
    --to=covici@ccs.covici.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).