From: Alexandre Duret-Lutz <adl@lrde.epita.fr>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45855@debbugs.gnu.org
Subject: bug#45855: 28.0.50; gnus does not start if one of the nntp backend fails to authenticate
Date: Tue, 19 Jan 2021 08:53:35 +0100 [thread overview]
Message-ID: <87wnw9e51c.fsf@lrde.epita.fr> (raw)
In-Reply-To: <87zh15mog7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 19 Jan 2021 07:27:04 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So I'm unable to reproduce this problem. Does (setq debug-on-error t)
> give you a backtrace?
Here:
Debugger entered--Lisp error: (nntp-authinfo-rejected . "Password rejected")
signal(nntp-authinfo-rejected "Password rejected")
#f(compiled-function () #<bytecode -0x100b464ebb0792ba>)()
nntp-with-open-group-function(nil "news.lrde.epita.fr" nil #f(compiled-function () #<bytecode -0x100b464ebb0792ba>))
nntp-request-newgroups("Mon, 18 Jan 2021 18:33:40 +0100" "news.lrde.epita.fr")
gnus-request-newgroups("Mon, 18 Jan 2021 18:33:40 +0100" (nntp "news.lrde.epita.fr" (nntp-open-connection-function nntp-open-ssl-stream) (nntp-port-number 563) (nntp-address "news.lrde.epita.fr")))
gnus-ask-server-for-new-groups()
gnus-find-new-newsgroups()
gnus-setup-news(nil nil nil)
#f(compiled-function () #<bytecode -0xf05a054e1413c45>)()
gnus-1(nil nil nil)
gnus(nil)
funcall-interactively(gnus nil)
call-interactively(gnus nil nil)
command-execute(gnus)
Here is what I see when I do it by hand:
% gnutls-cli -p 563 news.lrde.epita.fr
[...]
200 news.lrde.epita.fr InterNetNews NNRP server INN 2.6.3 ready (no posting)
AUTHINFO USER adl
381 Enter password
AUTHINFO PASS dummy
481 Authentication failed
next prev parent reply other threads:[~2021-01-19 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 11:09 bug#45855: 28.0.50; gnus does not start if one of the nntp backend fails to authenticate Alexandre Duret-Lutz
2021-01-19 6:27 ` Lars Ingebrigtsen
2021-01-19 7:53 ` Alexandre Duret-Lutz [this message]
2021-01-19 14:57 ` Lars 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnw9e51c.fsf@lrde.epita.fr \
--to=adl@lrde.epita.fr \
--cc=45855@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).