When STARTTLS is not wanted...

When STARTTLS is not wanted...

[Michael Welsh Duggan]

[-- 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)

Re: When STARTTLS is not wanted...

[Lars Magne Ingebrigtsen]

Michael Welsh Duggan <md5i@md5i.com> writes:

> 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'm guessing that your starttls installation doesn't work?  Perhaps
because starttls-gnutls-program is "gnutls-cli", and it needs --insecure
to actually work?

I'll add a version of your patch to those that really want a network and
no tls.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: When STARTTLS is not wanted...

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I'll add a version of your patch to those that really want a network and
> no tls.

On the other hand: If the user really has specified `network', isn't it
a bit...  odd for nnimap to decide to use STARTTLS anyway?  If they want
STARTTLS, they can say 'starttls.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: When STARTTLS is not wanted...

[Michael Welsh Duggan]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> I'll add a version of your patch to those that really want a network and
>> no tls.
>
> On the other hand: If the user really has specified `network', isn't it
> a bit...  odd for nnimap to decide to use STARTTLS anyway?  If they want
> STARTTLS, they can say 'starttls.

Since STARTTLS can fail if it is not set up correctly, I agree.  If it
were something that simply "always worked", I might consider otherwise.

-- 
Michael Welsh Duggan
(md5i@md5i.com)