Re: Un-Murdering Cyrus?

If you have just the one backend, then its mailboxes.db is complete and accurate.  All you have to do is remove the mupdate entries from cyrus.conf AND imapd.conf and you're good to go.  I do it all the time on my local dev setup. On 03/22/2018 02:47 PM, Nic Bernstein wrote: Friends, I've

Un-Murdering Cyrus?

Friends, I've got a Cyrus installation, at a client with roughly a dozen locations around the UA, which started life about 20 years ago and was split into a murder -- 2 frontends, 1 backend, 1 mupdate master -- several years back.  At the time of the split, there were plans to geographically

Re: SIEVE not workin in 3.0.5

Am Donnerstag, 22. März 2018, 13:19:37 CET schrieb Ken Murchison: > This was fixed with > https://github.com/cyrusimap/cyrus-imapd/commit/73af8e19546f235f6286cc9147a > 3ea74bde19ebb#diff-020bdafc26d65dd6a68af1d78b11a456 > > This fix will be in 3.0.6. Thanks! So i will bump the repo maintainer

Re: SIEVE not workin in 3.0.5

Am Donnerstag, 22. März 2018, 12:54:00 CET schrieben Sie: > The same issue was discussed in this thread: > > > Seems very similiar, even if he comes from a upgrades cyrus system while i did a new / fresh one. > There

Re: SIEVE not workin in 3.0.5

This was fixed with https://github.com/cyrusimap/cyrus-imapd/commit/73af8e19546f235f6286cc9147a3ea74bde19ebb#diff-020bdafc26d65dd6a68af1d78b11a456 This fix will be in 3.0.6. On 03/22/2018 07:47 AM, Niels Dettenbach via Info-cyrus wrote: Dear all, on a fresh installed cyrus 3.0.5 under

Re: SIEVE not workin in 3.0.5

The same issue was discussed in this thread: There was no resolution, AFAICT. I'd suggest opening an issue on GitHub: --On 22. März 2018 um 12:47:48 +0100 Niels

SIEVE not workin in 3.0.5

Dear all, on a fresh installed cyrus 3.0.5 under Linux i can't get SIEVE reacting to anything (in LMTP). It seems lmtpd avoid calling sieve/timsieve because it did not "find" any "defaultbc" script (which is there). After tracing the process i found this - it seems the lmtp does not recognize