Migration from Berkeley (Unix) Mailbox Format to Cyrus

Unix systems and the out-of-the-box UW IMAP server both store mail messages in Berkeley mail format (also referred to as mbox, Unix, or /var/mail format) mail folders. Many sites that use Berkeley format move their users onto a Cyrus server to take advantage of the quota and ACL support that Cyrus offers. In this section, we’ll walk though the steps involved in such a migration. Source code for the tools we used to accomplish the migration are provided in Appendix A .

How Do I Know My Mail Is Berkeley Format?

If your mail setup matches six out of seven of the criteria below, then you’re storing mail in Berkeley format:

  • There is no mail server—users log on to a Unix machine and run a mail program to read their mail.

  • There is a mail server, but it’s the UW IMAP server, running out-of-the-box with no special site configuration.

  • Each user’s incoming mail is stored in a spool directory, such as /var/mail or /var/spool/mail.

  • Each user’s incoming mail is stored within a single file, named after the user.

  • Mail folders are stored in the user’s home directory.

  • Mail reading is done with programs such as Elm, PINE, mail (1), rmail (1), or mailx (1).

  • Each mail folder contains a header, blank line, and message body, and delimits messages with the From header line.[43]

Issues

When converting a production mail system to Cyrus, several issues need to be taken into consideration to make the conversion go smoothly.

User-driven versus ...

Get Managing IMAP now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.