Package: cyrus-imapd
Architecture: amd64
Version: 3.6.1-4+deb12u3
Severity: minor
The configuration file /etc/cyrus.conf from the package cyrus-imapd begin
with
START {
# do not delete this entry!
recover cmd="/usr/sbin/cyrus ctl_cyrusdb -r"
# this is only necessary if idlemethod is set to "idled" in imapd.conf
#idled cmd="idled"
# this is useful on backend nodes of a Murder cluster
# it causes the backend to synchronize its mailbox list with
# the mupdate master upon startup
#mupdatepush cmd="/usr/sbin/cyrus ctl_mboxlist -m"
# this is recommended if using duplicate delivery suppression
delprune cmd="/usr/sbin/cyrus expire -E 3"
# this is recommended if caching TLS sessions
tlsprune cmd="/usr/sbin/cyrus tls_prune"
}
with this two lines:
delprune cmd="/usr/sbin/cyrus expire -E 3"
tlsprune cmd="/usr/sbin/cyrus tls_prune"
the cyrus daemon would wait those two starting commands to be ended before
starting anything else.
Knowing the delprune can take long time (90 minutes for 3000 accounts),
it's not usable.
If you check the official documentation :
https://www.cyrusimap.org/imap/reference/manpages/configs/cyrus.conf.html
you can see in the “Examples” section the delprune are in the
EVENTS {
checkpoint cmd="ctl_cyrusdb -c" period=30
delprune cmd="cyr_expire -E 3" at=0400
tlsprune cmd="tls_prune" at=0400
}
so no blocking when the service start.
It would be help to follow the official config who can work in much more
case than the one provided by debian package.
And they are not any downside of the official configuration, the «delprune»
would be running every day at 0400 instead one time at starting.
regards
