gnus fail windows 24

gnus fail windows 24

[William Stevenson]

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

I'm running 23.3.1 with gnus just fine, but 24 hangs retrieving imap from
gmail.

OS: Windows Vista
version: "GNU Emacs 24.0.50.1 (i386-mingw-nt6.0.6002) of 2011-03-14 on 3249CTO"

*Messages*
Opening nnfolder server on archive...done
Opening nnimap server on gmail...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...failed
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com --protocols ssl3'...failed
Opening TLS connection with `openssl s_client -connect imap.gmail.com:993 -no_ssl2 -ign_eof'...done
Opening TLS connection to `imap.gmail.com'...done
Quit trying to open server nnimap+gmail
Opening nnimap server on gmail...failed: 
Opening nntp server on Gmane...done
8 new newsgroups have arrived
Checking new news...
Reading active file from archive via nnfolder...done
Reading active file via nndraft...done
Checking new news...done
Warning: Opening nnimap server on gmail...failed: ; Quit trying to open
server nnimap+gmail

Note: gnutls-cli fails here as I renamed it, gnus was ignoring this
option I've set in .gnus

(setq imap-ssl-program "c:/cygwin/bin/openssl.exe s_client -ssl3 -quiet
-connect %s:%p")

[-- Attachment #2: .gnus file --]
[-- Type: application/emacs-lisp, Size: 2245 bytes --]

Re: gnus fail windows 24

[Lars Magne Ingebrigtsen]

William Stevenson <yhvh2000@gmail.com> writes:

> I'm running 23.3.1 with gnus just fine, but 24 hangs retrieving imap from
> gmail.

[...]

> Opening TLS connection to `imap.gmail.com'...
> Opening TLS connection with `gnutls-cli --insecure -p 993
> imap.gmail.com'...failed
> Opening TLS connection with `gnutls-cli --insecure -p 993
> imap.gmail.com --protocols ssl3'...failed
> Opening TLS connection with `openssl s_client -connect
> imap.gmail.com:993 -no_ssl2 -ign_eof'...done
> Opening TLS connection to `imap.gmail.com'...done
> Quit trying to open server nnimap+gmail
> Opening nnimap server on gmail...failed: 

[...]

> Note: gnutls-cli fails here as I renamed it, gnus was ignoring this
> option I've set in .gnus
>
> (setq imap-ssl-program "c:/cygwin/bin/openssl.exe s_client -ssl3 -quiet
> -connect %s:%p")

The `imap-ssl-program' variable isn't used in Emacs 24.  Change
`tls-program' instead to be what you want it to be.

Anyway, when it hangs, can you look in the "*imap log*" and "*nnimap
... gmail ... *" buffers and see what's in them?

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

Re: gnus fail windows 24

[William Stevenson]

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

> William Stevenson <yhvh2000@gmail.com> writes:
>
>> I'm running 23.3.1 with gnus just fine, but 24 hangs retrieving imap from
>> gmail.
>
> [...]
>
>> Opening TLS connection to `imap.gmail.com'...
>> Opening TLS connection with `gnutls-cli --insecure -p 993
>> imap.gmail.com'...failed
>> Opening TLS connection with `gnutls-cli --insecure -p 993
>> imap.gmail.com --protocols ssl3'...failed
>> Opening TLS connection with `openssl s_client -connect
>> imap.gmail.com:993 -no_ssl2 -ign_eof'...done
>> Opening TLS connection to `imap.gmail.com'...done
>> Quit trying to open server nnimap+gmail
>> Opening nnimap server on gmail...failed: 
>
> [...]
>
>> Note: gnutls-cli fails here as I renamed it, gnus was ignoring this
>> option I've set in .gnus
>>
>> (setq imap-ssl-program "c:/cygwin/bin/openssl.exe s_client -ssl3 -quiet
>> -connect %s:%p")
>
> The `imap-ssl-program' variable isn't used in Emacs 24.  Change
> `tls-program' instead to be what you want it to be.
>
> Anyway, when it hangs, can you look in the "*imap log*" and "*nnimap
> ... gmail ... *" buffers and see what's in them?

I removed the reference to `imap-ssl-program', left `tls-program' as
default, quit the hang.

"*nnimap ... gmail.com ... *" buffer contents:
* OK Gimap ready for requests from 81.99.65.51 d63if288461wej.35

(line ends with ^M character)
There was no "*imap log*" buffer.

Swapping in my normal `imap-ssl-program' setting for `tls-program'
resulted in much the same output, (renamed %s to %h ).

Re: gnus fail windows 24

[Lars Magne Ingebrigtsen]

William Stevenson <yhvh2000@gmail.com> writes:

> "*nnimap ... gmail.com ... *" buffer contents:
> * OK Gimap ready for requests from 81.99.65.51 d63if288461wej.35
>
> (line ends with ^M character)
> There was no "*imap log*" buffer.

If there was no log buffer, then it means that it hung while waiting for
the connection to complete, which is quite odd, since the greeting from
Gmail looks perfectly OK.

Could you try to (setq debug-on-quit t), `C-g' when it hangs and see if
you get a backtrace?  That might tell us where it's hanging.

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

Re: gnus fail windows 24

[William Stevenson]

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

> William Stevenson <yhvh2000@gmail.com> writes:
>
>> "*nnimap ... gmail.com ... *" buffer contents:
>> * OK Gimap ready for requests from 81.99.65.51 d63if288461wej.35
>>
>> (line ends with ^M character)
>> There was no "*imap log*" buffer.
>
> If there was no log buffer, then it means that it hung while waiting for
> the connection to complete, which is quite odd, since the greeting from
> Gmail looks perfectly OK.
>
> Could you try to (setq debug-on-quit t), `C-g' when it hangs and see if
> you get a backtrace?  That might tell us where it's hanging.
No "*Backtrace*" buffer

"*nnimap ... gmail ... *" buffer contents:
/usr/bin/bash: gnutls-cli: command not found

Process *nnimap* exited abnormally with code 127
/usr/bin/bash: gnutls-cli: command not found

Process *nnimap* exited abnormally with code 127
Loading 'screen' into random state -CONNECTED(00000110)
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 210 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
---
 done.
38616:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:184:.

Process *nnimap* exited abnormally with code 1


(non-printing character replaced with ".")

Re: gnus fail windows 24

[Lars Magne Ingebrigtsen]

William Stevenson <yhvh2000@gmail.com> writes:

> "*nnimap ... gmail ... *" buffer contents:
> /usr/bin/bash: gnutls-cli: command not found
>
> Process *nnimap* exited abnormally with code 127
> /usr/bin/bash: gnutls-cli: command not found
>
> Process *nnimap* exited abnormally with code 127

Right; that's normal...

> Loading 'screen' into random state -CONNECTED(00000110)
> ---
> no peer certificate available
> ---
> No client certificate CA names sent
> ---
> SSL handshake has read 0 bytes and written 210 bytes
> ---
> New, (NONE), Cipher is (NONE)
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> ---
>  done.
> 38616:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
> failure:s23_lib.c:184:.
>
> Process *nnimap* exited abnormally with code 1

That's not normal.  Apparently your openssl responds in such a way that
tls.el thinks that it connected successfully, but it really fails?

If you use openssl manually, are you able to connect successfully?

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

Re: gnus fail windows 24

[William Stevenson]

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

> If you use openssl manually, are you able to connect successfully?
Yup.

I've fixed this by just monkeying around here, changed 'tls-program' to
"c:/cygwin/bin/openssl.exe s_client -connect %h:%p -no_ssl2 -ign_eof"

Best guess is it seems I have 2 versions of openssl, cygwin and
GnuWin32, and the line endings from the GnuWin32 version were clashing
with however I've configured my .emacs (and promptly forgotten). This is
more intuition than anything - for example I now see no ^M chars in the
"*nnimap ... gmail ..." buffer but in every line in the "*imap log*".

Thanks for the help, if there's anything else I can report I'd be glad
to.