nnimap-server-port being ignored?

nnimap-server-port being ignored?

[Malcolm Purvis]

I have an imap server that it accessed via a custom port (being a ssh
tunnel to the real machine):

 (nnimap "home"
	 (nnimap-address "localhost")
	 (nnimap-server-port 11143)
	 (nnimap-stream network)
	 )

However, I get a Connection Refused error when I try to talk to the
server.  After some digging, it looks like the value of
nnimap-server-port is being ignored, because passing the correct value
to open-protocol-stream makes things work again:

diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 4bdf96b..b259a61 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -350,7 +350,7 @@ textual parts.")
        (push (format "%s" nnimap-server-port) ports))
       (destructuring-bind (stream greeting capabilities)
          (open-protocol-stream
-          "*nnimap*" (current-buffer) nnimap-address (car (last ports))
+          "*nnimap*" (current-buffer) nnimap-address "11143";(car (last ports))
           :type nnimap-stream
           :shell-command nnimap-shell-program
           :capability-command "1 CAPABILITY\r\n"

The value of 'ports' at this point is ("11143" "143" "imap").

Thanks,

Malcolm

-- 
		     Malcolm Purvis <malcolmp@xemacs.org>

Re: nnimap-server-port being ignored?

[Lars Magne Ingebrigtsen]

Malcolm Purvis <malcolmp@xemacs.org> writes:

> The value of 'ports' at this point is ("11143" "143" "imap").

Ah, right.  The wrong orders.  I've now fixed this.

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

Re: nnimap-server-port being ignored?

[Tommy Kelly]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> Ah, right.  The wrong orders.  I've now fixed this.

I've pulled this fix but my tunneled server is still burst. I see this
in *Messages*:

Warning: Opening nnimap server on tunl...failed: ; Denied server nnimap+tunl; Opening nnimap server on tunl...failed: ; Unable to open server nnimap+tunl due to: make client process failed: connection refused, :name, *nnimap*, :buffer, *nnimap localhost 10143  *nntpd**, :host, localhost, :service, imap

I reverted to 5.13 and it still works fine so I don't think anything has
changed at my server side. Relevant .gnus:

(setq gnus-secondary-select-methods
      '(
	 (nnimap "tunl"          ; Via the tunnel
	 	(nnimap-stream network)
	 	(nnimap-address "localhost")
	 	(nnimap-server-port 10143)
		)
	(nnimap "gapp"          ; Direct from Google Apps
		(nnimap-address "imap.gmail.com")
		(nnimap-server-port 993)
		)
	(nnimap "pers"          ; Direct from Gmail
		(nnimap-address "imap.gmail.com")
		(nnimap-server-port 993)
		)
	)
      )

Tommy

Re: nnimap-server-port being ignored?

[Lars Magne Ingebrigtsen]

Tommy Kelly <tommy.kelly@verilab.com> writes:

> I've pulled this fix but my tunneled server is still burst. I see this
> in *Messages*:
>
> Warning: Opening nnimap server on tunl...failed: ; Denied server nnimap+tunl; Opening nnimap server on tunl...failed: ; Unable to open server nnimap+tunl due to: make client process failed: connection refused, :name, *nnimap*, :buffer, *nnimap localhost 10143  *nntpd**, :host, localhost, :service, imap

Hm.

Could you say

`M-x debug-on-entry RET open-protocol-stream RET'

and see what port number it's actually called with?

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

Re: nnimap-server-port being ignored?

[Tommy Kelly]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Could you say
>
> `M-x debug-on-entry RET open-protocol-stream RET'
>
> and see what port number it's actually called with?

Sorry, been traveling. Looks like you already fixed the problem, yes?

Tommy

Re: nnimap-server-port being ignored?

[Lars Magne Ingebrigtsen]

Tommy Kelly <tommy.kelly@verilab.com> writes:

> Sorry, been traveling. Looks like you already fixed the problem, yes?

If by "you" you mean "all y'all", then yes.  But not me.  :-)

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