OK, let me know what you find out.
Working on it.
I didn't change the logic if/when SSL_accept() fails, because if its an SSL_wrapped process, there is nothing to fall back on (the application protocol hasn't started yet). Perhaps your dial-in clients take longer than 3 minutes to complete the handshake.
No, because it fails *immediately*.
Hmm, from this particular log, I don't see the debug message tellinng us that we're waiting for more input. When I test locally (over localhost), I always get at least in "-> waiting" log message before the "-> done" messsage.
Sure, for the most part I get those as well. But there are exceptions. And of course in principle SSL_get_error() can return something unexpected the first time around. So that's what I'll be looking for.
--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
.:.:.:.Skype: shagedorn.:.:.:.Attachment:
pgpZ9mfH4qVul.pgp
Description: PGP signature
---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
