A Few Notes on Cyrus IMAP System

[Matthew Carpenter]

After a recent bout with a Cyrus email server, I thought I'd pass on what I'd 
learned...

Summary:  Troubleshooting email delivery failure

The email indexing and attributes database was corrupt.  After much digging 
and troubleshooting, the appropriate files were restored from backup,

------------- notes-------------
Cyrus IMAP has basically 3 important filesystem trees (SuSE layout):
* /usr/lib/cyrus/bin/	- Location of executables and utilities
* /var/spool/imap/	- Location of emails themselves
* /var/lib/imap/		- Metadata: indexing, attributes, seen or not, etc....

/var/lib/imap/tls_sessions.db and /var/lib/imap/deliver.db can be deleted and 
the service restarting will recreate them.  Not so the other files in this 
directory.

/usr/lib/cyrus/bin/reconstruct allows the reconstruction of an email file from 
the spool.  All emails will show up as unread/new.

#cyrus on freenode IRC is a helpful place to look for assistance.  Be sure to 
not be offensive (like away messages, etc...)


-- 
Matthew Carpenter 
matt at eisgr.com                          http://www.eisgr.com/

Enterprise Information Systems
* Network Server Appliances
* Security Consulting, Incident Handling & Forensics
* Network Consulting, Integration & Support
* Web Integration and E-Business
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.linux-sxs.org/pipermail/linux-users/attachments/20051206/8767ebb9/attachment.pgp