From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43047@debbugs.gnu.org
Subject: bug#43047: 28.0.50; Closing Gnus server then searching it results in unrecoverable breakage
Date: Fri, 16 Oct 2020 10:03:10 -0700 [thread overview]
Message-ID: <87eely5cj5.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87362e2jo7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 16 Oct 2020 18:57:12 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>>> Debugger entered--Lisp error: (error "NPR/imaps Name or service not known")
>>>> make-network-process(:name "*nnimap*" :buffer #<buffer *nnimap NPR
>>>> nil *nntpd**> :host "NPR" :service "imaps" :nowait nil :tls-parameters
>>>> nil :coding nil)
>>>
>>> Reading this bug report, it's somewhat unclear what the problem is. Is
>>> "NPR" really the name of the server you're connecting to, or is that the
>>> problem? That Gnus is trying to connect to "NPR"?
>>
>> Yes, the server is correct: nnimap+NPR. Once I get that error above, I
>> can't reconnect, and get the same error for all nnimap backends.
>
> But is "NPR" the domain name of the server you're trying to connect to?
> Or is it the Gnus server name?
It's just the label of the server:
(nnimap "NPR"
(nnimap-address "localhost")
(nnimap-stream network)
(gnus-message-archive-group "nnimap+NPR:Sent")
(nnimap-authenticator login)
(nnimap-user "eric@paper-republic.org"))
next prev parent reply other threads:[~2020-10-16 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 18:12 bug#43047: 28.0.50; Closing Gnus server then searching it results in unrecoverable breakage Eric Abrahamsen
2020-10-16 8:21 ` Lars Ingebrigtsen
2020-10-16 16:54 ` Eric Abrahamsen
2020-10-16 16:57 ` Lars Ingebrigtsen
2020-10-16 17:03 ` Eric Abrahamsen [this message]
2021-08-27 17:44 ` Lars Ingebrigtsen
2021-08-27 18:33 ` Eric Abrahamsen
2021-08-27 18:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eely5cj5.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=43047@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.