From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: p0.42 can't `A T'?
Date: 10 Nov 1998 17:20:37 -0500 [thread overview]
Message-ID: <vxk4ss742bu.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "10 Nov 1998 14:23:49 -0500"
I wrote:
> Signaling: (error "Can't fetch thread from backends that don't support NOV")
I set out to chase this error down. What I found was that
nntp-server-xover was nil. I didn't understand why that would be the
case, so I ended that Gnus session, which was a day or so old, exited
XEmacs entirely, and started again, intending to find out when
nntp-server-xover was nilified.
The error doesn't occur in the fresh XEmacs at all.
/mutter/ irreproducible bugs /mumble/
Are there circumstances in which XOVER can fail even though the server
accepts the command? I can only imagine that, at some point when Gnus
sent an XOVER, though INN would have accepted it, nonetheless INN must
have returned some complaint which Gnus (mis-?)interpreted as an
complete XOVER failure.
next prev parent reply other threads:[~1998-11-10 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-10 19:23 Karl Kleinpaste
1998-11-10 22:20 ` Karl Kleinpaste [this message]
1998-11-13 18:12 ` Lars Magne Ingebrigtsen
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=vxk4ss742bu.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).