> What you see there is correct behaviour. You are going straight into SSL > negotiation after connect, so the server does nothing - it is the client's > responsibility to send the first SSL message.
that´s exactly what i wanted to know! > > ps (by the way): "openssl s_client -connect 127.0.0.1:993" says > > > > <code> > > 082659992:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake > > failure:s3_pkt.c:1193:SSL alert number 40 > > 82659992:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake > > failure:s3_pkt.c:590: > > </code> > > Now that's *not* correct. Something is going wrong with the SSL negotiation; > the server might be dropping the connection early. This could mean, for > example, that you don't have a certificate on the server. that error only happens on localhost, when i try from outside to public ip x.x.x.x:993 everything works fine. thanks @brain and others! so, the thread can be closed. i dont know how to mark it is solved. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
