From: Steinar Bang <sb@metis.no>
Subject: Re: Forcing authentication on a server
Date: 05 Feb 1998 17:38:53 +0100 [thread overview]
Message-ID: <whn2g66m76.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Steinar Bang's message of "05 Feb 1998 15:54:52 +0100"
>>>>> Steinar Bang <sb@metis.no>:
> Platform: qgnus-0.22, GNU emacs 19.34, SPARC, Solaris 2.5
> The FAQ says the following about using an NNTP server with
> authentication:
> (add-hook 'nntp-server-opened-hook 'nntp-send-authinfo)
> I've also tried
> (add-hook 'nntp-server-opened-hook 'nntp-send-nosy-authinfo)
Actually this seemed to work some of the time... but I've been unable
to reproduce it. I seemed to introduce a behaviour where it *always*
asked for username and password on a "g" command in *Group*.
Not really what I was looking for, but I was able to read an article
on that server.
next prev parent reply other threads:[~1998-02-05 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-05 14:54 Steinar Bang
1998-02-05 15:32 ` Andy Eskilsson
1998-02-05 16:38 ` Steinar Bang [this message]
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
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=whn2g66m76.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).