No subject

So, we do have some nasty bug in the packages, or something bad happened to
your system that damaged the statoverrides.

> For people who find this bug report when searching a tip what to do - you must
> run these two commands (as root, of course):
> 
> dpkg-statoverride --add cyrus mail 755 /var/run/cyrus 
> dpkg-statoverride --add cyrus mail 750 /var/run/cyrus/socket
> 
> This should have been done by the package update that introduced the change to
> the rc.d script.

The postinst script should create them if they don't exist already.  In
fact, the cyrus-comon-2.2 postinst script, from package version
2.2.13-14+lenn3 has this:

dpkg-statoverride --list /var/lib/cyrus 2>&1 >/dev/null ||
                dpkg-statoverride --update --add cyrus mail 750 /var/lib/cyrus
dpkg-statoverride --list /var/spool/cyrus 2>&1 >/dev/null ||
                dpkg-statoverride --update --add cyrus mail 755 /var/spool/cyrus
dpkg-statoverride --list /var/spool/sieve 2>&1 >/dev/null ||
                dpkg-statoverride --update --add cyrus mail 755 /var/spool/sieve
dpkg-statoverride --list /var/run/cyrus 2>&1 >/dev/null ||
                dpkg-statoverride --update --add cyrus mail 755 /var/run/cyrus
dpkg-statoverride --list /var/run/cyrus/socket 2>&1 >/dev/null ||
                dpkg-statoverride --update --add cyrus mail 750 \
                                 /var/run/cyrus/socket

We need more data to find out what could be wrong.

So, what exactly happened when you installed the packages?  Is it a recent
install?  Did it happen after you removed a previous installed cyrus
package, or after an upgrade?

Does "dpkg --pending --configure" says it is trying to configure any cyrus
packages?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh