Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: mark@ixod.org (Mark T.B. Carroll)
Subject: Gnus agent: Baffling offline behaviour without LIST ACTIVE
Date: Sun, 06 Nov 2005 20:49:23 -0500	[thread overview]
Message-ID: <878xw1i5wc.fsf@ixod.org> (raw)

I have Gnus connect to a few NNTP servers. Each is marked (agent) in the
servers buffer. Everything works fine with downloading articles and looking
at them offline for all except one of the servers. In comparison with the
others, I can't see anything remarkable in its configuration. However, if I
poke around in News/agent I see that its active file is unusual in being
empty.

Indeed, it's the only server that doesn't support LIST ACTIVE. With Gnus
unplugged, I can't use any of its groups. However, here's the really
strange thing:

Gnus agent has downloaded all the articles in those groups. They're there
on disk, it just refuses to access them. Moreover, when plugged Gnus does a
GROUP for each of the relevant groups on that server, so it does have the
information it needs. And, it seems to need to go back to the server for
the articles even though they're already downloaded.

What's going on here? The active files for the other servers don't seem to
contain anything that Gnus wouldn't have got when it did the GROUP commands
instead of LIST ACTIVE on the one server I'm having trouble with. How can I
get it to deal with this server in the same agreeable manner as it does the
others, so that I can read news from it with Gnus unplugged?

(I apologise if this appears multiple times - I seem to have limited
control over Gnus so far! I'm aware of one accidental posting that I
immediately cancelled.)

-- Mark


                 reply	other threads:[~2005-11-07  1:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=878xw1i5wc.fsf@ixod.org \
    --to=mark@ixod.org \
    /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).