From: Jim Marshall <jmarshall99@qwest.net>
Subject: Not getting new news
Date: Sat, 29 May 2004 03:01:24 -0700 [thread overview]
Message-ID: <87oeo7eemj.fsf@mojo.chicken.com> (raw)
Hi,
I'm running Gnus 5.10.6, with a recentish CVS version of Emacs. I'm
having a problem with getting new articles from my main news server,
easynews.com. For some reason, the discussion groups I read there
don't show any new articles since April 21 when I first
start up Gnus.
There have, of course, been many articles actually posted since then,
and if I do M-g (for "gnus-topic-get-new-news-this-topic") on either
a group or topic before entering a group, then the message count will
be correctly updated, and upon entering the group, the messages since
April 21 will indeed be displayed. If I then quit Gnus and restart
it, the message counts and displays will again reflect the "April 21"
problem I'm having. Even if I manually save (via "s") before exiting,
upon restarting, there will again be shown the wrong message counts.
I've tried all three values of "gnus-read-active-file" (nil, t, and
'some), to no effect. I've turned off an on "gnus-read-newsrc-file"
and its "save" counterpart. I've tried with the agent enabled and
disabled. I've searched Usenet via Google groups, but haven't found
anything that has helped (this, along with the Gnus manual, is where I
got the idea to try the above).
Does anybody have any idea what might be the problem here? I have
only two servers configured, easynews and gmane, and gmane seems to
be working fine. Easynews is a binary-oriented newsserver, and it may
well be that their "active file" isn't updated often or even
correctly, but shouldn't setting "gnus-read-active-file" to nil get
around even that kind of a problem? I'm really at a loss here, and
hope someone might have at least some things to try.
reply other threads:[~2004-05-29 10:01 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=87oeo7eemj.fsf@mojo.chicken.com \
--to=jmarshall99@qwest.net \
/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).