From: garys@opusnet.com (Gary W. Swearingen)
Subject: gnus won't stop trying to get same article
Date: Thu, 15 Sep 2005 23:03:43 GMT [thread overview]
Message-ID: <s6fys6dja8.ys6@mail.opusnet.com> (raw)
While reading thru a newsgroup, gnus will go after an article
(probably the "next" one) and apparently the lousy news server
doesn't have it, but gnus keeps trying until I use C-g.
(I have to keep my eye on the modem light when reading news.)
Here's part of my *nntp-log*:
20050915T155203.845 news.opusnet.com ARTICLE 539049
20050915T155203.886 news.opusnet.com AUTHINFO USER xxxx
20050915T155203.927 news.opusnet.com AUTHINFO PASS yyyy
20050915T155218.961 news.opusnet.com ARTICLE 538940
20050915T155231.157 news.opusnet.com ARTICLE 538941
20050915T155252.260 news.opusnet.com ARTICLE 538942
20050915T155345.324 news.opusnet.com ARTICLE 538955
20050915T155405.823 news.opusnet.com ARTICLE 538980
20050915T155405.864 news.opusnet.com AUTHINFO USER xxxx
20050915T155405.904 news.opusnet.com AUTHINFO PASS yyyy
Last three lines repeat forever (with changing times, of course).
Is there a "try only 3 times" setting, or something?
Thanks.
reply other threads:[~2005-09-15 23:03 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=s6fys6dja8.ys6@mail.opusnet.com \
--to=garys@opusnet.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).