From: Andy Eskilsson <andy.eskilsson@telelogic.se>
Subject: Re: Forcing authentication on a server
Date: 05 Feb 1998 16:32:41 +0100 [thread overview]
Message-ID: <ksg1lyysme.fsf@telelogic.se> (raw)
In-Reply-To: Steinar Bang's message of "05 Feb 1998 15:54:52 +0100"
/ Steinar Bang <sb@metis.no> wrote:
| 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)
|
|
| But this only works on an NNTP server that demands authentication,
| right...?
Hmm shouldn't?? The functions above just sends the authinfo commands
if I read the code right, doesn't check if the server wants
authentification.
| New question: would it be an idea to add a general mechanism that
| would let you set username and password in the Group Info of a foreign
| NNTP group?
I vote for this!!! At the moment I have created my own function that I
point the authentification function at that sends the login and pass.
Uhm am I the only one having problems with hangs after entering
user/pass, pressing C-g fixes and I can continue to read news from
that server, but when gnus-async kicks away and I have answered
user/login I can't abort it with C-g.
/andy
BTW What is mode stream?? (Messing around with dnews servers, are
there any good docs for the extra commands and so on? I have a hard
time finding a RFC with for example XOVER in it
next prev parent reply other threads:[~1998-02-05 15:32 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 [this message]
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
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=ksg1lyysme.fsf@telelogic.se \
--to=andy.eskilsson@telelogic.se \
/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).