Re: nnimap with openssl stopping up after connecting in Windows

["Steven E. Harris" <seh@panix.com>]

[I apologize if this message already made it to the list once. My Emacs
 email-related configuration is not yet straightened out.]


Steinar Bang <sb@dod.no> writes:

> So the fix can be either:
>  - Make emacs stop changing LF to CRLF in this case

I'm happy to report that I'm posting this from within Emacs, and I think
I found the problem with this whole Windows-Emacs-with-Cygwin-tunneling
setup. It's the shell!

Check the value of `shell-file-name' in your Emacs instance. If, like
me, you started Emacs from within a Cygwin shell, this variable will
bear a value such as "zsh". But try this:

,----
| (let ((shell-file-name "C:/Program Files/emacs-22.3/bin/cmdproxy.exe"))
|   (gnus))
`----

or even just

,----
| (let ((shell-file-name "cmdproxy"))
|   (gnus))
`----

and see what happens. That's all it took -- after about four months of
occasional noodling -- to make it work.

There's also the variable `shell-command-switch' which may need
adjustment for some values of `shell-file-name'. Its default value of
"-c" seems to work properly with "cmdproxy".

[Some time passes...]

Well, maybe not. I still can't get this to work with STARTTLS, and now
I'm noticing that even if I set `shell-file-name' back to "zsh", nnimap
still works with openssl. If I include the form

  (nnimap-stream ssl)

in my select method definition for the IMAP server, it works. Without
that form, it tries to use STARTTLS, finds a Cygwin-compiled starttls
program, and fails as described previously.

I'd like to be more happy about this, but I'm confused.

-- 
Steven E. Harris