Courier by default uses "INBOX." as private IMAP namespace, so it has exactly the same problems as described with UW-IMAP above. Again, if you want the migration to be transparent for IMAP clients, see ["Namespaces"] how to set namespaces to be Courier-compatible.
Courier's courierimapsubscribed is compatible with Dovecot's subscriptions file, just rename it and remove the "INBOX." prefixes. (NOTE: with 0.99.x it's .subscriptions, with 1.0 it's subscriptions without the dot)
Courier's courierimapuiddb is compatible with Dovecot's dovecot-uidlist file, just rename it.
- Courier's message flags are compatible with Dovecot (as they are specified by the Maildir specification)
- Courier's message keywords implementation isn't Dovecot compatible and there is currently no easy way to migrate them.
See also the [http://bendiken.net/scripts/ courier2dovecot] script by Arto Bendiken.
See also the [http://www.aucontraire.net/scripts/mail/courier2dovecot.py courier2dovecot.py] script by Michael Watkins.
# normal home directories mail_location = maildir:~/Maildir # for virtual users mail_location = maildir:~/
For POP3 UIDL compatibility with Courier, the Dovecot configuration depends on the Courier version used:
- Courier version 0
# Courier version 0 (using maildir filenames) pop3_uidl_format = %f
- Courier version 1
# Courier version 1 (UID) pop3_uidl_format = %u
- Courier version 2 and early Courier version 3
# Courier version 2 (UIDVALIDITY and UID - you most likely want this) pop3_uidl_format = %v-%u
- Courier version 3 (younger versions)
Here everything has changed: Courier's UID data are now stored incourierpop3dsizelistand in a completely new format. But it's still possible to convert it to the format dovecot needs (link to perlscript and further configuration details will follow later).