File: features.rst.txt

package info (click to toggle)
cyrus-imapd 3.10.0~beta1-3
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 86,332 kB
  • sloc: ansic: 284,810; perl: 135,824; javascript: 9,562; sh: 5,728; yacc: 2,565; cpp: 2,147; makefile: 2,133; lex: 662; xml: 621; awk: 303; python: 279; asm: 262
file content (104 lines) | stat: -rw-r--r-- 2,862 bytes parent folder | download | duplicates (14)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
.. _imap-features:

========
Features
========

The Cyrus IMAP (Internet Message Access Protocol) server provides
access to personal mail, system-wide bulletin boards, news-feeds,
calendar and contacts through the IMAP, NNTP, CalDAV and CardDAV
protocols. The Cyrus IMAP server is a scalable enterprise groupware
system designed for use from small to large enterprise environments
using technologies based on well-established Open Standards.

A full Cyrus IMAP implementation allows a seamless mail and bulletin
board environment to be set up across one or more nodes. It differs
from other IMAP server implementations in that it is run on *sealed
nodes*, where users are not normally 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 software using
the IMAP, IMAPS, POP3, POP3S, KPOP, CalDAV and/or CardDAV protocols.

The private mailbox database design gives the Cyrus IMAP server large
advantages in efficiency, scalability, and administrability. 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.

Cyrus IMAP provisionally supports the emerging JMAP protocol standards,
when built for such.

The following documents show the full power of each feature that is
included with Cyrus IMAP.

Exceptions notwithstanding, most of this documentation does not involve
the :ref:`imap-rfc-support`.

Security and Authentication
---------------------------

.. toctree::
    :maxdepth: 1

    features/authentication-kerberos
    features/authentication-ldap
    features/authentication-sql
    features/access-control
    features/sealed-system

Mailbox Management
------------------

.. toctree::
    :maxdepth: 1

    features/automatic-creation-of-mailboxes
    features/namespaces
    features/virtual-domains
    features/mailbox-annotations
    features/mailbox-distribution

Message Management
------------------

.. toctree::
    :maxdepth: 1

    features/delayed-delete
    features/delayed-expunge
    features/message-annotations
    features/duplicate-message-delivery-suppression
    features/shared-seen-state
    features/server-side-filtering
    features/event-notifications

Calendar and Contact (DAV) Collection Management
------------------------------------------------

.. toctree::
    :maxdepth: 1

    features/caldav-collections
    features/dav-components
    features/dav-collection-mgmt
    features/carddav

Storage
-------

.. toctree::
    :maxdepth: 1

    features/mail-spool-partitions
    features/mailbox-metadata-partitions
    features/archiving
    features/quota
    features/single-instance-store

Load Management
---------------

.. toctree::
    :maxdepth: 1

    features/server-aggregation