Courier IMAPd expects the public and the private key in the same file ie:
-----BEGIN RSA PRIVATE KEY----- <snip> -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- <snip> -----END CERTIFICATE-----
If you don't do this it will say:
Aug 3 00:11:03 hoiho imapd-ssl: starttls: /usr/lib/courier/imapd.pem: error:0906D06C:PEM routines:PEM_read_bio:no start line
If you have multiple machines running courier-imap and your maildirs are stored on an NFS mount, read this:
# Setting IMAP_USELOCKS to 1 will use dot-locking to support concurrent # multiple access to the same folder. This incurs slight additional # overhead. Concurrent multiple access will still work without this setting, # however occasionally a minor race condition may result in an IMAP client # downloading the same message twice, or a keyword update will fail. # # IMAP_USELOCKS=1 is strongly recommended when shared folders are used.
If you don't, you'll find that when the same user connects at the same time, on different frontends, the aforementioned race condition will happen. It's a good way to eat 3M/s between the machine that lost the race and the NFS filer as it sits there looking for a file which the other machine has nuked.
While upgrading an exsisting setup using source build you may get an error in the sanity check during the make check phase.
This may be caused by global shared folders, if you have any.
To fix rename your shared-folders file then restart the make check.
Do not forget to reset your renamed shared-folderes file.
From what I could see it seems that the caputered output from the sanity check will list your shared folders along with the ones created for the sanity tests, this of cause does not match the output expected and hence the make will fail with an error.
No page links to CourierImapNotes.
