I remember squashing a bug on Debian's 2.1 master code that caused it not to process *all* available messages at every interaction (instead, it processed only one). This caused messages to pile up in busy sites and triggered the above issues. As I said, I think 2.2 does not have this bug, but it is something that could be checked.
Yup, and thanks very much for squashing that bug!
It looks to me like 2.2 does indeed still have it, the master code still only processes one message in each service loop.
-Jules --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
