From: Alex Branham <alex.branham@gmail.com>
To: 37221@debbugs.gnu.org
Subject: bug#37221: 27.0.50; gnus fails to open connection post-NSM update
Date: Wed, 04 Sep 2019 08:13:58 -0500 [thread overview]
Message-ID: <87sgpcdx0p.fsf@gmail.com> (raw)
In-Reply-To: <m2tv9tp23c.fsf@gmail.com> (Robert Pluim's message of "Tue, 03 Sep 2019 22:16:39 +0200")
On Tue 03 Sep 2019 at 22:16, Robert Pluim <rpluim@gmail.com> wrote:
> Alex> Sure thing, it's below. network-security-level is medium. If I do (setq
> Alex> nsm-trust-local-network t) then all seems to work as expected.
>
> Oh, thatʼs interesting. Youʼre using (nnimap-stream network), which
> will attempt STARTTLS with localhost, unless nsm-trust-local-network
> is t. (nnimap-stream plain) will turn off the attempted STARTTLS
> upgrade.
I tried chancing it to plain and get the same error with the same message.
> Could you try with nsm-trust-local-network nil, and
> nnimap-record-commands t ? That should produce an "*imap log*" buffer
> that might tell us more, perhaps with (setq debug-on-error t) for good
> measure.
When I tried this there was not an *imap log* buffer. When I set
nsm-trust-local-network to t there's an *imap log* buffer, though that's
not as useful I suppose. But at least the logging is working?
> Iʼll admit Iʼm at a loss as to why the recent nsm changes would cause
> this to start failing. Iʼm assuming thereʼs nothing interesting in
> "*Messages*", and youʼre not prompted for anything?
Correct, other than the message I originally reported (Warning: Opening
nnimap server on LocalMail...failed: ; Unable to open server
nnimap+LocalMail due to: Buffer *nnimap localhost nil *nntpd** has no
process)
Thanks,
Alex
next prev parent reply other threads:[~2019-09-04 13:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 16:56 bug#37221: 27.0.50; gnus fails to open connection post-NSM update Alex Branham
2019-09-02 9:33 ` Robert Pluim
2019-09-03 18:26 ` Alex Branham
2019-09-03 20:16 ` Robert Pluim
2019-09-04 13:13 ` Alex Branham [this message]
2019-09-04 13:37 ` Lars Ingebrigtsen
2019-09-04 14:00 ` Alex Branham
2019-09-04 14:16 ` Lars Ingebrigtsen
2019-09-04 14:24 ` Alex Branham
2019-09-04 14:35 ` Lars Ingebrigtsen
2019-09-04 14:51 ` Alex Branham
2019-09-04 14:56 ` Robert Pluim
2019-09-04 14:59 ` Lars Ingebrigtsen
2019-09-04 15:04 ` Robert Pluim
2019-09-04 15:04 ` Alex Branham
2019-09-04 15:25 ` Robert Pluim
2019-09-04 15:55 ` Alex Branham
2019-09-04 17:00 ` Robert Pluim
2019-09-04 17:06 ` Lars Ingebrigtsen
2019-09-04 17:21 ` Robert Pluim
2019-09-04 17:24 ` Lars Ingebrigtsen
2019-09-04 19:30 ` Robert Pluim
2019-09-04 19:37 ` Lars Ingebrigtsen
2019-09-04 20:37 ` Robert Pluim
2019-09-04 20:41 ` Lars Ingebrigtsen
2019-09-04 21:49 ` Robert Pluim
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=87sgpcdx0p.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=37221@debbugs.gnu.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).