[Pkg-Cyrus-imapd-Debian-devel] Re: Experimental cyrus22 packages (preview of upcoming official packages) available on alioth

[Sven Mueller]

Edward J. Shornock wrote on 04/04/2005 21:59:

 >> I downloaded the binary packages on 2005-Apr-03, and previously had
 >> Cyrus21-* installed.  The upgrade went through without difficulty.


Good to hear.

  > ..and websieve-0.62, after modifying the package from unstable to
  > depend upon libcyrus-imap-perl22.

I filed a wishlist bug against websieve to incorporate an equivalent
change into the sid/sarge package of websieve.

  > Both (seem) to be working
  > flawlessly here on my home mail server after a day of use.  If that
  > changes, I'll post a follow-up.

Since I'm experiencing difficulties in that area:
Do you use SSL connections with cyrus22? I.e. do you provide imap/pop3
over SSL?

I tried to, but I got the following error messages which I simply don't
know what might have gone wrong:

Apr  8 04:09:29 mail1 cyrus/imaps[32041]: unable to get private key from
'/etc/ssl/private/mail.incase.de.key'
Apr  8 04:09:29 mail1 cyrus/imaps[32041]: TLS server engine: cannot load
cert/key data
Apr  8 04:09:29 mail1 cyrus/imaps[32041]: error initializing TLS
Apr  8 04:09:29 mail1 cyrus/imaps[32041]: Fatal error: tls_init() failed
Apr  8 04:09:29 mail1 cyrus/imaps[32041]: DBERROR db4: Database handles
open during environment close
Apr  8 04:09:29 mail1 cyrus/imaps[32041]: DBERROR: error exiting
application: Invalid argument

however, the SSL key file is OK, since postfix is using exactly the same
file to provide SSL encrypted SMTP. And I really can't see what might
cause that DBERROR messages. My guess is that the DBERROR messages are a
problem originally caused by imapd being unable to load the keyfile. But
I have no idea why cyrus can't read it.

Does anyone have any idea regarding that issue?

cu,
sven