Cyrus IMAP server

From Wikipedia, the free encyclopedia

POSSIBLE COPYRIGHT INFRINGEMENT

If you have just labeled this page as a possible copyright infringement, please add the following to the bottom of Wikipedia:Copyright_problems/2006_December_12/Articles
* {{subst:article-cv|Cyrus IMAP server}} from [http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusHistory]. ~~~~

The previous content of this page appears to infringe on the copyright of the text from the source(s) below and is now listed on Wikipedia:Copyright problems:

http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusHistory

Do not edit this page until an administrator has resolved this issue.

To write a new article without infringing material, follow this link to a temporary subpage.

State that you have done so on this article's discussion page.

Note that simply modifying copyrighted text is not sufficient to avoid copyright infringement—it is best to write the article from scratch. An administrator will move the new article into place once the issue is resolved.

If you hold the copyright to this text and permit its use under the terms of the GNU Free Documentation License:

Explain this on this article's discussion page, then either display a notice to this effect at the site of original publication or send an e-mail from an address associated with the original publication to permissions-en at wikimedia dot org or a postal letter to the Wikimedia Foundation. These messages must explicitly permit use under the GFDL.

Note: Articles on Wikipedia must be written from a neutral point of view and must be verifiable in reliable published sources; copyright issues aside, your text may not be appropriate for inclusion in Wikipedia.

If this text is in the public domain or is already under a license suitable for Wikipedia:

Explain this on this article's discussion page, with reference to evidence.

Unless the copyright status of the text on this page is clarified, it will be deleted one week after the time of its listing.

Posting copyrighted material without the express permission of the copyright holder is a violation of applicable law and of Wikipedia policy.
If you have questions about copyright, see Copyright FAQ.
Those who repeatedly post copyrighted material will be blocked from further editing.
Temporarily, the original posting is still accessible for viewing in the page history.
You are welcome to submit original contributions.

Maintenance use only: {{subst:Nothanks-web|pg=Cyrus IMAP server|url=http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusHistory}} ~~~~

Cyrus IMAP server

Developer:	Carnegie Mellon University
Latest release:	2.2.13 / 2006-03-31
Preview release:	2.3.7 / 2006-07-11
OS:	Cross-platform
Use:	Mail Delivery Agent
License:	Open source
Website:	http://cyrusimap.web.cmu.edu/

The Cyrus IMAP server differs from other IMAP server implementations in that it is generally intended to be run on sealed servers, where normal users are not permitted to log in. The mail spool uses a filesystem layout and format similar to the Maildir format used by other popular email servers such as qmail, Courier, Dovecot, etc. Cyrus IMAP's spool format is said to have improved performance and scalability to Maildir, and is stored in parts of the filesystem that are private to the Cyrus IMAP system. Users can access mail through the IMAP/IMAP-S, POP3/POP3-S or KPOP protocols.

The Cyrus IMAP server supports server-side mail filtering through the implementation of a mail filtering language called Sieve.

The private mailbox database design gives the server large advantages in efficiency, scalability, and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies.

[edit] History

Prior to 1994, Carnegie Mellon University used the locally-developed and non-standard AndrewMailSystem (AMS) for its email communication needs. Originally written in the early 80s as part of the Andrew Project, it was very advanced for its day. However, it had major scalability issues. It was also desired to move to a standards compliant mail system that met or exceeded the feature set of AMS with an emphasis on disconnected operation and scalability. Scalability was sought both in simultaneous online accesses and large mailboxes.

The Cyrus Project was started at Carnegie Mellon in 1994 to attempt to meet these goals. The following are some documents that date from that era and describe the original goals of the project. As such they may be somewhat out of date.

The first year that all of Carnegie Mellon's incoming freshmen were placed on the Cyrus server was 1998 (class of 2002). In December of 2001, bboard access (which had been being mirrored from AMS to Cyrus), was cut over to Cyrus completely. AMS was finally phased out in May of 2002.

As development on the project progressed, it became clear that further scalability was required, and additional reliability was desired beyond that which would be provided from a single machine configuration. To meet these goals, the CyrusMurder was developed, and after several revisions it was deployed to Carnegie Mellon in the summer of 2002.

SOURCE -- RobSiemborski - 24 Jul 2003