
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Mail Delivery Agents
|
301
When you installed Cyrus IMAP, whether from binary packages or
from source code, a new user (cyrus) should have been created and
given ownership of most Cyrus IMAP files. As with any other good
service daemon, Cyrus IMAP runs as a special nonprivileged user
rather than root most of the time.
The three other settings in Example 9-26 that I had to customize were tls_cert_file,
tls_key_file,andtls_cipher_list. These are analogous to OpenLDAP’s slapd.conf
parameters
TLSCertificateFile, TLSCertificateKeyFile,andTLSCipherSuite, respec-
tively, which I mention because the certificate/key files specified here are the same
ones I used for OpenLDAP on this system.
This is because in my example scenario, I’m running Cyrus IMAP on the same server
I’m running OpenLDAP on; there’s no reason to use different server certificates and
keys for services running on the same machine. (However, I did copy both files from
/etc/openldap to /var/lib/imap, to simplify ownership/permissions management.)
If my LDAP service were running on a separate host, I would create a new TLS cer-
tificate/key pair for my LDAP server, using exactly the same procedure I described
earlier (i.e., via the command
openssl req -new -x509 -nodes -out slapdcert.pem
-keyout slapdkey.pem -days 365
). Regardless,