Cyrus Update for Kolab 3.4

[Daniel Hoffend]

Hi Andy

the patch I've applied is this one:
https://cyrus.foundation/cyrus-imapd/commit/imap/cyr_expire.c?id=24c597fac9a464940eb6c4fc5131df0b39d5c86a

The package management update request in OBS
https://obs.kolabsys.com/request/show/1056

I'm not sure which edge cases this all applies to at least in my 
scenario
I could verify the fix on the command line using manual execution of the
delayed expunge command:

# Before

 > su - cyrus -c "/usr/lib/cyrus-imapd/cyr_expire -E 4 -X 69 -v"
 > Expunging deleted messages in mailboxes older than 69.00 days
 > Expired 0 and expunged 0 out of 0 messages from 0 mailboxes

This message also repeats in the mail.log every night around 4am as
configured in the imapd.conf.

# Before (but doing it for a single user instead for all mailboxes)

 > su - cyrus -c "/usr/lib/cyrus-imapd/cyr_expire -E 4 -X 69 -u 
<my at email>"
 > Expunging deleted messages in mailboxes older than 69.00 days
 > Expired 0 and expunged 14952 out of 69960 messages from 86 mailboxes

So delayed expunge mode worked ... but only of single users in my case.
After manually iterating of all accounts I manually expunged 40k mails.

# Now (after installing the patch)

 > su - cyrus -c "/usr/lib/cyrus-imapd/cyr_expire -E 4 -X 69 -v"
 > Expunging deleted messages in mailboxes older than 69.00 days
 > Expired 0 and expunged 31 out of 75546 messages from 607 mailboxes
Maybe it doesn't apply to all scenarios but the commit notes and my test
before pushing the fix into OBS made me confident that it's okay. Maybe
it's limited to the multidomain setups, who knows.

Too bad no one realized it that 2 days before the 3.4 release it got
in the cyrus repo.

What version if cyrus package/version did/do you've installed? Does
your mail.log reports that messages are regularly are being expunged?
Cause my mail.log was reporting every night that nothing got expunged
up until now.

--
Regards
Daniel Hoffend

------ Originalnachricht ------
Von: "Andy Kopciuch" <akopciuch at bddf.ca>
An: users at lists.kolab.org; "Daniel Hoffend" <dh at dotlan.net>
Gesendet: 09.12.2015 10:51:45
Betreff: Re: Cyrus Update for Kolab 3.4

>On Wednesday December 9 2015 08:43:48 Daniel Hoffend wrote:
>>  Hello Kolab Admins
>>
>>  Last night I've just pushed out a small fix for Cyrus which fixed a
>>  behaviour with expunging/removing mail messages once they got flagged
>>  for deletion. Basically the delayed expunging didn't worked at all as
>>  configured with the default configuration. They bug got fixed in
>>  february 2 days before the 3.4 release but nobody noticed it ...
>>
>>  Well ... why am I writing this to the mailing list? Maybe you want to
>>  keep an eye on your performance or you're wondering what's causing 
>>the
>>  huge disk free change :-)
>>
>>  Just on my small installation around 40k out of 120k mails got 
>>expunged
>>  (which freed up around 1GB of space). If you think how many spams you
>>  delete over time or how many mails you're moving to different folders
>>  while the origingal mail will be flagged for deletion that number 
>>isn't
>>  unusual ... But maybe your installation has a higher user count and
>>  therefore more load/changes when the fixed expunging process kicks 
>>in.
>>
>
>
>Do you have a link to this bug?  I couldn't find anything on the kolab 
>bug
>tracker nor the cyrus bug tracker.
>
>Was this an unreported problem, with a patch available?
>
>I am not experiencing problems with the delayed expunge.  200+ user
>installation in production 4+ months.   The disk use remains at the 
>same pace
>prior to the kolab upgrade (was not using delayed expunge previous).
>
>I totally believe you! ;)  I know others have reported the same 
>problem.   I'm
>just curious as to the details, and what exactly the problem was.
>
>
>Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5595 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20151209/c6a0860d/attachment-0001.bin>