On Fri, 2003-01-10 at 13:27, Chris Toshok wrote:
I do here. Well, I just fixed a post-1.2.1 regression that was keeping it from working, but 1.2.1 should work.. Are you connecting to port 389 and doing STARTTLS or connecting to 636? Here's my server output (with my latest patch): connection_read(9): checking for input on id=0 TLS trace: SSL_accept:before/accept initialization TLS trace: SSL_accept:SSLv3 read client hello A TLS trace: SSL_accept:SSLv3 write server hello A TLS trace: SSL_accept:SSLv3 write certificate A TLS trace: SSL_accept:SSLv3 write server done A TLS trace: SSL_accept:SSLv3 flush data TLS trace: SSL_accept:error in SSLv3 read client certificate A TLS trace: SSL_accept:error in SSLv3 read client certificate A connection_get(9): got connid=0 connection_read(9): checking for input on id=0 TLS trace: SSL_accept:SSLv3 read client key exchange A TLS trace: SSL_accept:SSLv3 read finished A TLS trace: SSL_accept:SSLv3 write change cipher spec A TLS trace: SSL_accept:SSLv3 write finished A TLS trace: SSL_accept:SSLv3 flush data Chris
That looks like the log when I connect with mozilla-mail. I tried using 389/Always and 636 (Always greyed out). Neither seem to work for me. tjb -- ======================================================================= | Thomas Baker email: tjb unh edu | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | =======================================================================
Attachment:
signature.asc
Description: This is a digitally signed message part