From: Steinar Bang <sb@metis.no>
Subject: Re: Attempted forced authentication on an NNTP server
Date: 09 Feb 1998 09:13:56 +0100 [thread overview]
Message-ID: <wh4t29yz3v.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "08 Feb 1998 21:02:46 +0100"
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Steinar Bang <sb@metis.no> writes:
>> I'm trying to do
>> (add-hook 'nntp-server-opened-hook 'nntp-force-unsecure-authinfo)
>> where nntp-force-unsecure-authinfo is the function in the patch
>> attached below.
>>
>> But I get the same kind of flaky behaviour as when I'm using
>> nntp-send-nosy-authinfo here, ie.: it didn't work at first, I just got
>> an "error: 411 No such group".
> You need the "mode reader" thing in the hook as well. Put
> `(require 'nntp)' in there before modifying the hook.
Hm... I was already running Gnus, and did the add-hook thingies in the
*scratch* buffer. nntp-send-mode-reader was in the hook already
I've tried both
(add-hook 'nntp-server-opened-hook 'nntp-send-nosy-authinfo)
which puts nntp-send-nosy-authinfo first, and
(add-hook 'nntp-server-opened-hook 'nntp-send-nosy-authinfo t)
which puts it at the end (and yes,... with a remove-hook in between).
Currently I have
nntp-server-opened-hook's value is (nntp-send-mode-reader nntp-send-nosy-authinfo)
and the behaviour is still flaky. Ie. it doesn't work right now. If
it starts working later on, I'll tell ya.
next prev parent reply other threads:[~1998-02-09 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-05 14:54 Forcing authentication on a server Steinar Bang
1998-02-05 15:32 ` Andy Eskilsson
1998-02-05 16:38 ` Steinar Bang
1998-02-06 10:09 ` Steinar Bang
1998-02-08 16:53 ` Attempted forced authentication on an NNTP server Steinar Bang
1998-02-08 20:02 ` Lars Magne Ingebrigtsen
1998-02-09 8:13 ` Steinar Bang [this message]
1998-02-09 16:29 ` Steinar Bang
1998-02-10 10:17 ` 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=wh4t29yz3v.fsf@norne.oslo.metis.no \
--to=sb@metis.no \
/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).