Re: nnimap with openssl stopping up after connecting in Windows

[Steinar Bang <sb@dod.no>]

>>>>> "Steven E. Harris" <seh@panix.com>:

> Steinar Bang <sb@dod.no> writes:
>>> I'd like to be more happy about this, but I'm confused.
>> 
>> So am I.  Perhaps we don't have the same problem, even...? :-/

> Perhaps. I'm also not confident that when I shut down this current
> Emacs instance and start up another one the IMAP connections will
> continue working. I'll have more time tonight or over the weekend to
> experiment more.

I tried the openssl binary linked to from here: http://www.openssl.org/related/binaries.html
(the "Win32 OpenSSL v0.9.8i Light").

The idea was that this program may be running as a native win32
application, and may (hopefully) not trigger the LF->CRLF translation
(which, to recap, isn't the actual problem.  The CRCRLF that results
from a CRLF hitting the conversion _is_ the problem (or at least I
think it is)).

It's another shot in the dark, but what the heck.

What I did:
 - I renamed the SUA community openssl executable to openssl_disabled.
 - I verified that I had no openssl in the path.
 - I added C:\OpenSSL\bin to the path.
 - I started a new cmd window, and verified that I now had the openssl
   executable in the path.
 - I ran the command "openssl s_client -connect myhost.dyndns.org:993"
   and verified that it connected to the IMAP server in what looked (to
   me) like a meaningful way
 - I started a new GNU emacs, and ran `M-x gnus-slave' in it, and it was
   less succsessful than the SUA openssl in opening the connection (it
   never said that it was able to open a connection and then timed out,
   like the SUA openssl does).  The " *nnimap* myserver" buffer
   contains: 

Process imap finished

Process imap<1> exited abnormally with code 1

Process imap<2> exited abnormally with code 1

 - Line separations in the " *nnimap* myserver" buffer are 0a, according
   to hexl-mode (ie. LF), and the status line displays "(Unix)" on the
   left side of the line
 - I started `M-x shell RET' and ran the command "openssl s_client
   -connect myhost.dyndns.org:993" and verified that it was able to open
   a connection to the IMAP server
 - I also started `M-x shell RET' on the emacs process running `M-x gnus
   RET' that was started before changing the path, and tried the same
   command, and verified that it had no openssl in its path

So... I know I have the new openssl executable in a way that can be
executed from inside emacs, but I still haven't been able to test if it
behaves nicer than SUA openssl (and presumably also cygwin openssl?) in
the " *nnimap* myhost" buffer.

Could it be that this openssl communicates with cmd.exe in another way
than using stdout and stdin...?

The speculations continue...