Bug#686110: cyrus-imapd: Corrupted databases can exhaust logging diskspace

[Jamie Thompson]

Package: cyrus-imapd
Version: 2.4.16-1
Severity: normal

Following a power failure my tls_sessions.db file became corrupted (UPS
is currently out of commission - anyway). When the server restarted, I
did not notice this fact and would not do so until my next logcheck
email (or an attempt to check my mail). Unfortunately, within a few
hours my logfiles ended up being full of cyrus's infinite unsuccessful
startup attempts, resulting in 6GB of logfiles, which so happened to
take my server down.

Ideally Cyrus should try to recover the databases, if that fails,
delete the session-specific recreateable ones (i.e. tls_sessions.db)
and try again, and if it is still unable to start, stop trying as
without intervention it's just wasting electricity and disk space.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cyrus-imapd depends on:
ii  cyrus-imapd-2.4  2.4.16-1

cyrus-imapd recommends no packages.

cyrus-imapd suggests no packages.

-- no debconf information