Re: nnimap with openssl stopping up after connecting in Windows

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:

> So I guess the right thing to do here, is to make sure there is no form
> of end-of-line translation going on in the nnimap buffer.

> I wonder what the correct approach here, is?
>   (set-buffer-process-coding-system 'undecided 'undecided)

This is what I tried.  Then there was no time out wait, and connecting
to the imap server immediately failed, with the following messages in
the minibuffer:

Opening nnimap server on myserver...
Unable to open server nnimap+myserver due to: No process
Unable to open server nnimap+myserver, go offline? (y or n) 
Opening nnimap server on myserver...failed

Trying to run (imap-disable-multibyte) in the *scratch* buffer gives the
following stack trace:
Debugger entered--Lisp error: (error "No process")
  signal(error ("No process"))
  error("No process")
  set-buffer-process-coding-system(undecided undecided)
  (progn (set-buffer-process-coding-system (quote undecided) (quote undecided)))
  (if (fboundp (quote set-buffer-process-coding-system)) (progn (set-buffer-process-coding-system ... ...)))
  (when (fboundp (quote set-buffer-process-coding-system)) (set-buffer-process-coding-system (quote undecided) (quote undecided)))
  imap-disable-multibyte()
  eval((imap-disable-multibyte))
  eval-last-sexp-1(t)
  eval-last-sexp(t)
  eval-print-last-sexp()
  call-interactively(eval-print-last-sexp)

So I guess set-buffer-file-coding-system is the one to try next...