| 1 |
==================== |
| 2 |
Sealed System Design |
| 3 |
==================== |
| 4 |
|
| 5 |
Cyrus IMAP is designed to run on *sealed system*, meaning that no |
| 6 |
user-related information needs to be available to the POSIX system, |
| 7 |
aside from the user and group Cyrus IMAP itself runs under. |
| 8 |
|
| 9 |
This eliminates the requirement for any of the service's users to hold |
| 10 |
POSIX account information attributes, and eliminates the need for |
| 11 |
Cyrus IMAP to maintain a super-privileged process allowed to substitute |
| 12 |
user. |
| 13 |
|
| 14 |
The message spool directory or directories are held privately by the |
| 15 |
Cyrus IMAP software, and can be accessed by user through IMAP, POP, NNTP |
| 16 |
or JMAP protocols. |
| 17 |
|
| 18 |
This design concept vastly increases the efficiency, scalability and |
| 19 |
security of Cyrus IMAP, and makes it easier to configure, maintain, |
| 20 |
troubleshoot and administer a Cyrus IMAP environment. |
| 21 |
|
| 22 |
.. NOTE:: |
| 23 |
|
| 24 |
Since all files and directories are held by the user and group that |
| 25 |
Cyrus IMAP runs under, any filesystem quota being used does not |
| 26 |
apply to anyone other than this user and group, voiding the ability |
| 27 |
to count disk usage towards a billing account's quota. |
| 28 |
|
| 29 |
Back to :ref:`imap-features` |