Discussion:
imap and openssl on Windows
(too old to reply)
Holger Sparr
2010-09-30 15:49:52 UTC
Permalink
Hi,

I have problems to read my mail:

.gnus.el

(setq gnus-secondary-select-methods '((nnimap "xxx"
(nnimap-address "imap.server.de")
(nnimap-server-port 993)
(nnimap-authenticator login)
(nnimap-stream ssl)))

There will be no server response to the imap command send.

*imap-log*

| * OK The Microsoft Exchange IMAP4 service is ready.
| 1 NOOP
| * BYE Connection is closed. 13
| done
| depth=2 C = DE, O = DFN-Verein, OU = DFN-PKI, CN = DFN-Verein PCA Global - G01
| verify error:num=20:unable to get local issuer certificate
| verify return:0
| read:errno=0
| 2 CAPABILITY

In contrast, connecting to the server via command line with cmdproxy.exe I get:

cmdproxy.exe "openssl s_client -connect imap.server.de:993"

| * OK The Microsoft Exchange IMAP4 service is ready.
| . noop
| . OK NOOP completed.
| . logout
| * BYE Microsoft Exchange Server 2007 IMAP4 server signing off.
| . OK LOGOUT completed.
| read:errno=0

I tried several settings for imap-client-eol and several addtitional flags for
openssl through imap-ssl-program.

Do you have any ideas?

Thanks in advance.

Holger Sparr
Lars Magne Ingebrigtsen
2010-09-30 17:57:02 UTC
Permalink
Post by Holger Sparr
*imap-log*
| * OK The Microsoft Exchange IMAP4 service is ready.
| 1 NOOP
| * BYE Connection is closed. 13
cmdproxy.exe "openssl s_client -connect imap.server.de:993"
| * OK The Microsoft Exchange IMAP4 service is ready.
| . noop
It looks like the MS Exchange server doesn't understand tagged commands,
which is really weird.

Anyway, nnimap has been rewritten completely in the development version
of Gnus/Emacs, and it's been reported to work with MS Exchange, so this
may or may not work now if you install development Gnus.
--
(domestic pets only, the antidote for overdose, milk.)
***@gnus.org * Lars Magne Ingebrigtsen
Loading...