Bill Williamson wrote:
> I used mkimapdcert, both with an untouched imapd.cnf, and with my changing > "localhost" to my ip address. > Both times give me this in the log when I try to connect (oe 6): > > Oct 9 09:34:20 (none) imapd-ssl: Connection, ip=[::ffff:63.103.217.132] > Oct 9 09:34:20 (none) imapd-ssl: Unexpected SSL connection shutdown. > Oct 9 09:34:20 (none) imapd-ssl: Unexpected SSL connection shutdown. Do you run POP/SSL too? Did you make a cert for the POP server with mkpopdcert? Does the IMAP server have the same name as the POP server, like mail.domain.com? Did you connect to the POP server with the same client that you are now attempting to connect to IMAP with? If the answer to all these questions is "yes", then your client sees a different certificate than the one it knows for the server, smells nasty tricks and refuses to connect. The same can happen if you made a certificate, connected, and then made a new certificate. Delete all (your own) certificates from the client, copy imap.pem over pop.pem or vice versa and try again. Z ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
