New Mail Stuff

From Syscore

This is a discussion/notes page regarding planning & implementing a new email storage & retrieval system at UMBC. Under heavy investigation is Cyrus from CMU. It seems to lend itself to our ethos of distrubuted horizontal scaling quite well.

• Mail Migration FAQ
• Copy of the CYRUS distribution documentation
• WebSieve for editing Sieve mail filters.
  • CMU's how-to-use sieve documentation
  • UAlbany's WebSieve instructions

Contents 1 Sizing and Configuration 2 Incremental Migration Plan 3 Changes Required 3.1 Mail Filtering 3.2 IMAP Configuration 3.3 Shared Folders

Sizing and Configuration

Our current load & user profile is very similar to the one at CMU, so using their current sizing and configuration as a baseline is probably reasonable.

• Cyrus Backend Instance Configuration
• Cyrus Frontend Instance Configuration

Incremental Migration Plan

It's probably safe to say that any migration around here needs to be incremental, and building a migration plan that allows the migration of key users for testing, while at the same time continuing to support our existing user bases' configuration will be important.

Changes Required

Mail Filtering

Cyrus natively uses the Sieve filtering language for mail filtering. While we can migrate OIT-created procmail filters that were made via our WebAdmin interface, we will not attempt to migrate custom procmail rules.

IMAP Configuration

Shared Folders