Project Summary
Analyzed
about 2 months
ago.
based on code collected
about 2 months
ago.
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 mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through the IMAP, POP3, or KPOP protocols.
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.
Quick Reference
- Project Links:
-
Homepage
Download
- Code Locations:
-
git://git.cyrusimap.org/cyrus-im...
- Licenses:
- CMU
- Similar Projects:
-
- Managers:
- Jeroen van Meeuwen
In a Nutshell, Cyrus IMAP...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with decreasing Y-O-Y commits -
...
took an estimated 66 years of effort (COCOMO model)
starting with its first commit in July, 1993
ending with its most recent commit about 1 year ago
Activity
30 Day SummaryJul 2 2016 — Aug 1 2016
|
12 Month SummaryAug 1 2015 — Aug 1 2016
|
