Sebastian Hagedorn wrote: > Thanks. I will try this patch as soon as I can, but it's clearly not the > only issue, because the same thing happens with POP processes. Here's an > example for one: > > (gdb) bt > #0 0x0096441e in __read_nocancel () from /lib/tls/libc.so.6 > #1 0x00ac02f7 in BIO_new_socket () from /lib/libcrypto.so.4 > #2 0x00abe2b2 in BIO_read () from /lib/libcrypto.so.4 > #3 0x00fcfe13 in ssl23_read_bytes () from /lib/libssl.so.4 > #4 0x00fcec51 in ssl23_get_client_hello () from /lib/libssl.so.4 > #5 0x00fce712 in ssl23_accept () from /lib/libssl.so.4 > #6 0x00fd2c9a in SSL_accept () from /lib/libssl.so.4 > #7 0x08052cb3 in shut_down () > #8 0x0804e513 in shut_down () > #9 0x0804d58c in ?? () > #10 0x00000001 in ?? () > #11 0x08dd6848 in ?? () > #12 0x00000000 in ?? () OK. What version of OpenSSL? Are they imaps/pop3s processes, or are your clients using STARTTLS? Are you sure that you're not running out of entropy? Have you tried adding the '-U 1' option to the offending services in cyrus.conf? -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University ---- 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