From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: When STARTTLS is not wanted...
Date: Mon, 27 Sep 2010 23:38:18 -0400 [thread overview]
Message-ID: <87hbhawn9x.fsf@maru.md5i.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On the machine on which my IMAP server resides, I connect via
(nnimap-stream network). After the STARTTLS changes, I get the
following instead:
Warning: Opening nnimap server on localimap...failed: ; Denied server
nnimap+localimap; Opening nnimap server on localimap...failed: ; Unable
to open server nnimap+localimap due to: Buffer *nnimap localhost nil
*nntpd** has no process
I've never used STARTTLS before, so I have no idea what I may or may not
be doing incorrectly. In order to get up and running again, I have made
the following patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 804 bytes --]
diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 4be9153..14d66dd 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -52,7 +52,7 @@ it will default to `imap'.")
(defvoo nnimap-stream 'ssl
"How nnimap will talk to the IMAP server.
-Values are `ssl', `network', `starttls' or `shell'.")
+Values are `ssl', `network', `network-no-tls', `starttls' or `shell'.")
(defvoo nnimap-shell-program (if (boundp 'imap-shell-program)
(if (listp imap-shell-program)
@@ -285,8 +285,8 @@ textual parts.")
(port nil)
(ports
(cond
- ((eq nnimap-stream 'network)
- (open-network-stream
+ ((memq nnimap-stream '(network network-no-tls))
+ (open-network-stream
"*nnimap*" (current-buffer) nnimap-address
(setq port
(or nnimap-server-port
[-- Attachment #3: Type: text/plain, Size: 136 bytes --]
If this is the wrong way to approach the problem, I'm happy to submit
debugging information.
--
Michael Welsh Duggan
(md5i@md5i.com)
next reply other threads:[~2010-09-28 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 3:38 Michael Welsh Duggan [this message]
2010-09-29 15:00 ` Lars Magne Ingebrigtsen
2010-09-29 15:01 ` Lars Magne Ingebrigtsen
2010-09-29 15:35 ` Michael Welsh Duggan
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=87hbhawn9x.fsf@maru.md5i.com \
--to=md5i@md5i.com \
--cc=ding@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.
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).