text: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" ""> <html xmlns=""> <head> <meta name="generator" content="HTML Tidy, see" /> <title>Cyrus IMAP Server FAQ</title> <!-- $Id: faq.html,v 1.37 2006/11/30 17:11:16 murch Exp $ --> </head> <body> <h1>Cyrus IMAP Server FAQ</h1> <ul> <li><b>Using PAM</b> Under Linux when using PAM and shadow passwords, /etc/shadow needs to be readable by the Cyrus user.</li> <li><b>POP-Before-SMTP</b> It is not included in the default distribution because there is already a standard way of doing this with SMTP AUTH. Any good MTA and/or MUA should support SMTP AUTH, so we shouldn't have to create a hack in an unrelated service. However, if you would like to install it anyway, we recommend using <a href="">DRAC</a>, along with the patch available in <tt>contrib/drac_auth.patch</tt>.</li> <li><b>Using NFS</b> We don't recommend it. If you want to do it, it may possibly work but you may also lose your email or have corrupted <tt>cyrus.*</tt> files. You can look at the mailing list archives for more information.</li> <li><b>Using AFS/Coda</b> We don't recommend it. It's even less likely to work than NFS. If you want to do it, it may possibly work but you may also lose your email or have corrupted <tt>cyrus.*</tt> files. CMU's previous e-mail system, AMS, leveraged AFS extensively for storage (and transit) purposes. For various reasons it didn't scale particularly well and led to CMU's interest in IMAP. <p> Cyrus was designed to use a local filesystem with Unix semantics and a working mmap()/write() combination. AFS doesn't provide these semantics so won't work correctly.</p> </li> <li><b>Virtual hosting</b> - See <a href="install-virtdomains.html">virtual domains configuration</a>.</li> <li><b>dots in userids</b> - you can have a '.' in your username IF, AND ONLY IF, you use the <a href="altnamespace.html#unixhiersep">UNIX hierarchy convention</a>.</li> <li><b>renaming users</b> - Supported, but try to make sure that the user is not, and can not login when doing the rename. Otherwise user-meta may get corrupted and/or out of sync.</li> <li><b>plus addressing</b> - Plus addressing allows direct delivery to a particular mailbox (other than an INBOX). This is done in two ways. <p>The first way allows delivery to a subfolder of a specific user's INBOX. This is done via an address of the form: username+mailfolder@domain, which will deliver to the user's INBOX.mailfolder folder (or altnamespace equivalent). This submailbox must allow the posting user the 'p' right (generally, this means 'anyone' must have the 'p' right), otherwise the message will just be filed into the user's INBOX. <p>The second way is to form an address like [postuser]+mailfolder@domain. This will deliver into the mailbox 'mailfolder'. [postuser] is the string specified in the imapd.conf option of the same name, and may be the empty string. As before, the posting user will need to have the 'p' right on the mailbox. <p>For both methods, if 'mailfolder' is more than one level deep, you will need to conform to the hierarchy separator appropriate to your site. </li> <li><b>Performance/Capacity/Scaling</b> - See <a href="install-perf.html">the performance guide</a>.</li> </ul> <h2>Troubleshooting</h2> <dl compact="compact"> <dt><b>Q:</b> I'm getting syslog'd messages from the master process saying processes are "signaled to death by 10". What's up?</dt> <dd> <p><b>A:</b> If you're using Berkeley DB 3.0.55, try installing some <a href="">patches to Berkeley DB</a> available from <a href=""></a>.</p> </dd> <dt><b>Q:</b> I've used <tt>saslpasswd2</tt> to create CRAM-MD5 secrets, but imapd doesn't say <tt>AUTH=CRAM-MD5</tt>. Why?</dt> <dd> <p><b>A:</b> Make sure <tt>/etc/sasldb2</tt> is readable by the Cyrus user.</p> </dd> <dt><b>Q:</b> I'm using "<tt>sasl_pwcheck_method: saslauthd</tt>", but authentication isn't working.</dt> <dd> <p><b>A:</b> Make sure that the <tt>saslauthd</tt> daemon is running (you'll want to start it when the system boots). <tt>imapd</tt> is unable to connect to <tt>saslauthd</tt> if the following message appears in the logs:</p> <pre> Dec 6 12:58:57 mail3.andrew.cmu.edu imapd[1297]: cannot connect to saslauthd server </pre> <p>Make sure that <tt>saslauthd</tt> is running and that the cyrus user can access the unix domain socket (defaults to <tt>/var/run/mux</tt>). </dd> <dt><b>Q:</b> I'm getting messages about "duplicate_prune". What's wrong?</dt> <dd><p><b>A:</b> These messages look like </p>  Jan 14 13:46:24 grant ctl_deliver[9060]: duplicate_prune: opening /var/imap/deliverdb/deliver-z.db: No such file or directory </pre> <p>These messages are normal; one file is maintained for each user beginning with "x", "y", "z", etc. If you're first starting or you have no users beginning with these letters, these messages are completely normal and can be ignored.</p> </dd> <dt><b>Q:</b> I'm getting a message about "<tt>imapd: could not getenv(CYRUS_SERVICE); exiting</tt>" in my <tt>imapd.log</tt>. What's wrong?</dt> <dd> <p><b>A:</b> Remove all <tt>imap</tt>, <tt>pop</tt>, <tt>lmtp</tt> and <tt>sieve</tt> lines from <tt>[x]inetd.conf</tt> and restart <tt>[x]inetd</tt>. Cyrus is run out of its own "master" process.</p> </dd> <dt><b>Q:</b> How do I use different SSL/TLS certificates for imap and pop?</dt> <dd> <p><b>A:</b> Specify the different certs using the appropriate options in <tt>imapd.conf</tt>. Read <tt>imapd.conf(5)</tt> for details.</p> </dd> <dt><b>Q:</b> My KPOP client is complaining about TLS keys. What should I do?</dt> <dd> <p><b>A:</b> Disable TLS for the kpop service. Either set <tt>tls_pop3_cert_file</tt> to <b>disabled</b> in <tt>imapd.conf</tt> (which will also disable SSL/TLS for pop3), or use a separate config file for kpop. For example, change the kpop service in <tt>cyrus.conf</tt> to something like:</p> <pre> kpopReturn</a> to the Cyrus IMAP Server Home Page </body> </html>