Differences between version 4 and predecessor to the previous major change of CourierImapNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, November 30, 2005 7:22:44 pm | by MichaelJager | Revert |
| Older page: | version 3 | Last edited on Saturday, January 10, 2004 5:07:42 pm | by JohnMcPherson | Revert |
@@ -1,13 +1,36 @@
+!SSL
+
Courier [IMAP]d expects the public and the private key in the same file ie:
-
-----BEGIN RSA PRIVATE KEY-----
+<verbatim>
+
-----BEGIN RSA PRIVATE KEY-----
<snip>
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
<snip>
-----END CERTIFICATE-----
+</verbatim>
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
+<verbatim>
+
Aug 3 00:11:03 hoiho imapd-ssl: starttls: /usr/lib/courier/imapd.pem: error:0906D06C:PEM routines:PEM_read_bio:no start line
+</verbatim>
+
+
+!NFS mounted maildirs
+
+If you have multiple machines running courier-imap and your maildirs are stored on an NFS mount, read this:
+
+<verbatim>
+# 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.
+</verbatim>
+
+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.
----
CategoryMailNotes
