[Kolab-devel] [issue2436] delprune setting in cyrus.conf

[Richard Bos]

New submission from Richard Bos <ml at radoeka.nl>:

This is an information issue a kind of "why ... this":

While upgrade the cyrus package on openSUSE, the cyrus.conf file was modified,
which resulted in the following diff:

# diff -u cyrus.conf.2008-01-31 cyrus.conf
--- cyrus.conf.2008-01-31       2008-01-31 13:52:28.000000000 +0100
+++ cyrus.conf  2008-01-31 13:52:28.000000000 +0100
@@ -40,7 +40,7 @@
   checkpoint   cmd="ctl_cyrusdb -c" period=30

   # this is only necessary if using duplicate delivery suppression
-  delprune     cmd="cyr_expire -E 3" period=1440
+  delprune      cmd="cyr_expire -E 3" at=0400


The cyrus.conf file that comes with cyrus sources (normal.conf) has the
same (at=0400) setting (copy from that file below):
EVENTS {
  # this is required
  checkpoint    cmd="ctl_cyrusdb -c" period=30

  # this is only necessary if using duplicate delivery suppression,
  # Sieve or NNTP
  delprune      cmd="cyr_expire -E 3" at=0400

  # this is only necessary if caching TLS sessions
  tlsprune      cmd="tls_prune" at=0400
}

Is there a special reason to use period=1440 instead of at=0400?  Or is the
at=0400 later added to the normal.conf instead of the period=1440?

Is period=1440 okay?  At may mean that the expire command runs during
busy traffic hours (high load) on the server, which is not desired.

----------
messages: 13526
nosy: rbos
priority: bug
status: unread
title: delprune setting in cyrus.conf
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue2436>
________________________________________________