Hi, On 13 Feb 2022, at 23:37, ellie timoney wrote:
> Your earlier email shows "chk_cyrus" complaining. I'm not familiar with this
> tool, and our tests don't run it. Looking at git history, it hasn't had
> substantial work in some time, so I wonder if the tool is simply out of date,
> and complaining about something perfectly normal that it hasn't been updated
> to recognise. Alas, when it finds the error that causes it to bail out, it
> doesn't bother to report _what the error was_. D'oh!
regarding this point: we’re still on Cyrus 2.4 (sigh), and we run this job
monthly:
/usr/lib/cyrus-imapd/chk_cyrus 2>/dev/null | /usr/bin/perl -nle
's/\./\//g;/(^.*) uid/;print "\"$1\""'| /bin/sort | /usr/bin/uniq |
/usr/bin/xargs -rn 1 /usr/lib/cyrus-imapd/reconstruct
It runs reconstruct on all mailboxes that chk_cyrus complains about. When your
server is running stable, there might not be anything to do, but there were
times when we had multiple mailboxes with issues per month.
I think that’s a useful tool to have. Is the idea that it’s not required
anymore in current versions, or just that nobody has thought of it?
Cheers,
Sebastian
--
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
smime.p7s
Description: S/MIME digital signature
This is a multi-part message in MIME format... ------------=_1644910982-986921-1--
