Cyrus was designed to use a local filesystem with Unix semantics and a working mmap()/write() combination. AFS doesn't provide these semantics so won't work correctly.
The first way allows delivery to a subfolder of a specific user's INBOX. This is done via an address of the form: username+mailfolder@domain, which will deliver to the user's INBOX.mailfolder folder (or altnamespace equivalent). This submailbox must allow the posting user the 'p' right (generally, this means 'anyone' must have the 'p' right), otherwise the message will just be filed into the user's INBOX.
The second way is to form an address like [postuser]+mailfolder@domain. This will deliver into the mailbox 'mailfolder'. [postuser] is the string specified in the imapd.conf option of the same name, and may be the empty string. As before, the posting user will need to have the 'p' right on the mailbox.
For both methods, if 'mailfolder' is more than one level deep, you will need to conform to the hierarchy separator appropriate to your site.
A: LMTP protocol differs from SMTP in that it causes the Cyrus to return, after the final "." of the DATA command, one reply for each recipient. If, for example, a server is given a transaction for two recipients, delivery to the first succeeds, and delivery to the second encounters a temporary failure condition, the MTA will get a separate response for each recipient and will only have to reattempt to deliver it to the second recipient. If using SMTP, only a single temporary failure response would be returned, and the entire transaction would have to be reattempted.
Furthermore, LMTP is superior to invoking command-line delivery agents from the MTA in that most ESMTP extensions are supported by LMTP, without having to extend any interfaces.
Lastly, because LMTP can be run over TCP, it allows you to run SMTP (and spam/virus scanning) and mailbox access on separate servers, thus allowing better scalability.
A: The key is not to over-subscribe any partitions. Avoid putting too many users on any one partition, such that read/write performance becomes unacceptable. Good RAID performance (plenty of read/write cache, and perhaps RAID 10 instead of RAID 5) will improve the number of users a partition can serve. To benefit from multiple partitions, each should be on its own set of disks, served by an unsaturated interface (FC, SCSI, SAS, SATA, etc) to the host running Cyrus.
See the performance guide or general performance guidelines. Also see metapartition_files and metapartition-name in imapd.conf.5 for additional configuration options which can help with performance, especially if you have access to high-speed storage (faster than disks).
A: Unless otherwise configured, Cyrus services only advertise PLAIN or plaintext login commands on encrypted connections (SSL-wrapped connections or after a successful STARTTLS command). This behavior can be changed with the use of the allowplaintext option in imapd.conf.5.
A: If you're using Berkeley DB 3.0.55, try installing some patches to Berkeley DB available from http://www.sleepycat.com/update/3.0.55/patch.3.0.55.html.
A: Make sure /etc/sasldb2 is readable by the Cyrus user.
A: Make sure that the saslauthd daemon is running (you'll want to start it when the system boots). imapd is unable to connect to saslauthd if the following message appears in the logs:
Dec 6 12:58:57 mail3.andrew.cmu.edu imapd[1297]: cannot connect to saslauthd server
Make sure that saslauthd is running and that the cyrus user can access the unix domain socket (defaults to /var/run/mux).
A: These messages look like
Jan 14 13:46:24 grant ctl_deliver[9060]: duplicate_prune: opening /var/imap/deliverdb/deliver-x.db: No such file or directory Jan 14 13:46:24 grant ctl_deliver[9060]: duplicate_prune: opening /var/imap/deliverdb/deliver-y.db: No such file or directory Jan 14 13:46:24 grant ctl_deliver[9060]: duplicate_prune: opening /var/imap/deliverdb/deliver-z.db: No such file or directory
These messages are normal; one file is maintained for each user beginning with "x", "y", "z", etc. If you're first starting or you have no users beginning with these letters, these messages are completely normal and can be ignored.
A: Remove all imap, pop, lmtp and sieve lines from [x]inetd.conf and restart [x]inetd. Cyrus is run out of its own "master" process.
A: Specify the different certs using the appropriate options in imapd.conf. Read imapd.conf(5) for details.
A: Disable TLS for the kpop service. Either set tls_pop3_cert_file to disabled in imapd.conf (which will also disable SSL/TLS for pop3), or use a separate config file for kpop. For example, change the kpop service in cyrus.conf to something like:
kpop cmd="pop3d -k -C /etc/kpopd.conf" listen="kpop"
then copy /etc/imapd.conf to /etc/kpopd.conf and remove the tls_* options.
A: First, complain to QUALCOMM because their STARTTLS implementation is broken. Eudora doesn't support TLSv1 (per RFC2246) and Cyrus requires it. If you really need this before it is fixed in Eudora, remove or comment out the following lines in tls.c:
if (tlsonly) {
off |= SSL_OP_NO_SSLv2;
off |= SSL_OP_NO_SSLv3;
}
Sep 11 17:23:55 ogg lmtpd[773]: DBERROR db3: 16 lockers Sep 11 17:23:55 ogg lmtpd[1409]: DBERROR db3: 17 lockers Sep 11 17:23:56 ogg lmtpd[1508]: DBERROR db3: 9 lockers Sep 11 17:23:56 ogg lmtpd[776]: DBERROR db3: 9 lockersWhat's wrong?
A: Nothing is wrong. These messages are logged whenever Berkeley DB encounters lock contention, but aren't necessarily problems. This is especially likely when you have an empty or small duplicate delivery database and are receiving a large volume of e-mail.
Berkeley DB 4.0 has a bug where the number of lockers isn't decremented properly, causing this number to be unreliable.
A: 8-bit characters are illegal in message headers. Following the principle of "be liberal in what you accept, and strict in what you send", Cyrus converts them to Xs. (Without a character set, having the 8-bit characters replaced with Xs is just as good as having them be any other 8-bit character, especially for sorting and searching). Alternatively, you can set "reject8bit: t" in imapd.conf to reject the messages outright. It might also be reasonable for Cyrus to support the use of a default character set, however thus far no one has done the work to do so (it would also involve QP-encoding the corrupted headers).
A: Trash folders, as they are commonly implemented (as actual IMAP mailboxes), do not fit the IMAP delete/expunge model very well. In fact, naive client implementations will get stuck in a situation where they cannot delete a message from a mailbox because they try to COPY it to the trash folder before deleting the message. This operation will fail due to the mailbox being over quota. This is separate from the fact that a specific mailbox name is not interoperable between clients (one might call it 'trash', another 'Trash', another 'Recycle Bin', etc)
Given the lack of protocol support for a trash folder, this is mostly a quality-of-implementation issue on the client side. There are a few options here:
A: Not really a Cyrus IMAPd question, this can be fixed by just removing the SASL plugins from where Cyrus SASL installed them (if no other applications require them), or by using the sasl_mech_list imapd.conf option to list only the mechanisms that you require.