Notes for Packagers¶
Prevent namespace clashes. We suggest renaming all binaries with
the front, including renaming the
The Cyrus team are looking to fix this in the core bundle in upcoming releases so packagers have less to do.
Sample configuration files¶
There are several samples of cyrus.conf(5) and
imapd.conf(5) located in the
doc/examples directory of
the distribution tarball. Please install these to your preferred
documentation directory (i.e.
/usr/share/doc/cyrus-imapd) as a
reference for your users.
The configuration file for master: cyrus.conf¶
When installing a predefined cyrus.conf(5) for your users, please pay attention to new features and how these may impact users. For example, for some time now, Cyrus has supported placing several standard DB files in temporary, or ephemeral, storage, such as memory backed filesystems like tmpfs (see below). This both boosts efficiency and ensures DB consistency in event of a crash or other system disruptive events. But, in light of this, actions which depend on the existence of these database files should not be placed in the START section of cyrus.conf(5).
A new section, DAEMON, was added to cyrus.conf(5) in version 2.5. Please consult cyrus.conf(5) for details. Please refer to the notes in Section Descriptions pertaining to the distinctions between START, EVENTS and DAEMON sections.
In brief, the sorts of things which should go into the different sections are:
Periodic processes which will be started by master(8) as specified.
Programs which should be spawned by master(8) which it should shut down and clean up after.
The configuration file for the various programs: imapd.conf¶
The sample imapd.conf(5) files must be adapted for use from site to site. Here, therefore, we'll attempt to point you towards some reasonable settings which take advantage of recent improvements and features, and may help guide you and your users to a better performing Cyrus installation.
Ephemeral files and temporary filesystems¶
In addition to Unix domain sockets and lock files, several databases
used by Cyrus programs may be located in temporary filesystems, such as
those backed by RAM (i.e. tmpfs, md, etc.). Here's a list of such
files. In this example, the filesystem
/run is on tmpfs:
Any process which depends on these files already existing should not be placed in the START section of cyrus.conf(5), or the server will not start as expected.
New default settings¶
A new stable series means the defaults for some settings may have changed. Please consult Upgrading to 3.8 for details.
New or improved features¶
A new stable series means new features, and improvements to existing features. Some of these may be features which previously were not considered ripe for packaging, but merit new consideration.
Listing named services through
/etc/services aids in cross-system
consistency and cross-platform interoperability. Furthermore, it enables
administrators and users to refer to the service by name (for example in
/etc/cyrus.conf, 'listen=mupdate' can be specified instead of
Some of the services Cyrus IMAP would like to see available through
/etc/services have not been assigned an IANA port number, and few have
The Cyrus IMAP server provides service interfaces via either TCP/IP
ports or Unix domain sockets. For the former, Cyrus requires that there
are proper entries in the host's
/etc/services file. The following
are required for any host using the listed services:
pop3 110/tcp # Post Office Protocol v3
nntp 119/tcp # Network News Transport Protocol
imap 143/tcp # Internet Mail Access Protocol rev4
nntps 563/tcp # NNTP over TLS
imaps 993/tcp # IMAP over TLS
pop3s 995/tcp # POP3 over TLS
kpop 1109/tcp # Kerberized Post Office Protocol
lmtp 2003/tcp # Lightweight Mail Transport Protocol service
smmap 2004/tcp # Cyrus smmapd (quota check) service
csync 2005/tcp # Cyrus replication service
mupdate 3905/tcp # Cyrus mupdate service
sieve 4190/tcp # timsieved Sieve Mail Filtering Language service
Make sure that these lines are present or add them if they are missing.