Uday S Reddy
2012-05-30 11:32:44 UTC
There seems to have been an update of stunnel, which is breaking VM's
automatic configuration code. It produced junk like this in the IMAP
process buffer:
Starting IMAP over SSL session Wed May 30 12:20:38 2012
-- connecting to imap.gmail.com:993
Clients allowed=125
stunnel 4.53 on i686-pc-cygwin platform
Compiled with OpenSSL 1.0.1 14 Mar 2012
Running with OpenSSL 1.0.1c 10 May 2012
Update OpenSSL shared libraries or rebuild stunnel
Threading:PTHREAD SSL:+ENGINE+OCSP Auth:LIBWRAP Sockets:POLL+IPv6
Reading configuration from file -R
-R: No such file or directory (2)
Cannot read configuration
This has *nothing* to do with OpenSSL libraries. VM couldn't figure out
that the version of stunnel needed a configuration file.
Putting the following in the .vm file cured the problem.
(setq vm-stunnel-wants-configuration-file t)
Che
automatic configuration code. It produced junk like this in the IMAP
process buffer:
Starting IMAP over SSL session Wed May 30 12:20:38 2012
-- connecting to imap.gmail.com:993
Clients allowed=125
stunnel 4.53 on i686-pc-cygwin platform
Compiled with OpenSSL 1.0.1 14 Mar 2012
Running with OpenSSL 1.0.1c 10 May 2012
Update OpenSSL shared libraries or rebuild stunnel
Threading:PTHREAD SSL:+ENGINE+OCSP Auth:LIBWRAP Sockets:POLL+IPv6
Reading configuration from file -R
-R: No such file or directory (2)
Cannot read configuration
This has *nothing* to do with OpenSSL libraries. VM couldn't figure out
that the version of stunnel needed a configuration file.
Putting the following in the .vm file cured the problem.
(setq vm-stunnel-wants-configuration-file t)
Che