Description of problem: cyrus-imapd daily cron job is broken. it keeps complaining about the account "cyrus" not being available, hence it doesn't acheieve its goal, and crond sends an email like this to the root : & Message 3: From root.org Mon Nov 16 03:18:04 2009 Return-Path: <root.org> X-Original-To: root Delivered-To: root.org From: Anacron <root.org> To: root.org Content-Type: text/plain; charset="ANSI_X3.4-1968" Subject: Anacron job 'cron.daily' on x3.ojuba.org Date: Mon, 16 Nov 2009 03:18:04 +0200 (EET) Status: RO /etc/cron.daily/cyrus-imapd: This account is currently not available. & Version-Release number of selected component (if applicable): rpm -qf /etc/cron.daily/cyrus-imapd cyrus-imapd-2.3.15-5.fc12.x86_64 How reproducible: Install cyrus-imapd, and you shall receive that problematic mail on the root user every day. Steps to Reproduce: 1.Install cyrus-imapd, make sure crond is running 2.Wait for 24+ hours 3.you will receive an error email like the above. Actual results: The cron job doesn't finish successfully and it give account-is-not-available error email. Expected results: should run smoothly without error email and have the mailbox list backup created. Additional info: I fixed it by adding "-s /bin/bash" to this line : $RUNUSER - cyrus -s /bin/bash -c "umask 077 < /dev/null ; /usr/lib/cyrus-imapd/ctl_mboxlist -d | gzip > ${MBOXLIST}.gz" so the solution is there, it requires someone else's validation and hence inclusion in the next update.
thanks for reporting this fixed in cyrus-imapd-2.3.15-6.fc12
cyrus-imapd-2.3.15-5.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/cyrus-imapd-2.3.15-5.fc11
cyrus-imapd-2.3.15-6.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/cyrus-imapd-2.3.15-6.fc12
cyrus-imapd-2.3.15-5.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
cyrus-imapd-2.3.15-6.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.