On Wed, 30 Nov 2016, at 08:37, Jason L Tibbitts III via Info-cyrus wrote:
> > "BG" == Bron Gondwana via Info-cyrus
> > writes:
>
> BG> If you use imapsync, it doesn't know about that, and will upload the
> BG> same message twice. 2.5 doesn't have the smarts to recognise that
> BG> it's t
> "BG" == Bron Gondwana via Info-cyrus
> writes:
BG> If you use imapsync, it doesn't know about that, and will upload the
BG> same message twice. 2.5 doesn't have the smarts to recognise that
BG> it's the same message.
Fun random question: Does anything blow up if you run hardlink on yo
Quota is a sum of byte sizes of raw unexpunged messages. It doesn't
deduplicate. Likely issue is incorrect quota_mailbox_used in the cyrus.index
header on 2.3. a reconstruct will fix those, then quota -f again.
It's not related to du.
The problem with imapsync is that it doesn't handle single i
Hello!
I'm using cyrus on Debian vm for several years but now, SSL starts to fail:
Nov 29 13:05:58 server1 cyrus/imaps[9595]: inittls: Loading
hard-coded DH parameters
Nov 29 13:05:58 server1 cyrus/imaps[9595]: imaps TLS negotiation
failed: [2801:0:140:f42:f3fa:b0b2:4ab1:8d10]
I tried wit
Well, I did another try to move to 2.5 branch.
I make some preparation this time:
1. took 2.5.10 and put twoskip & skiplist patches from master
[PATCH] cyrusdb: add "CYRUSDB_NOCOMPACT" open flag to avoid
[PATCH] twoskip: release the readlock in foreach every 256 misses
2. put mailboxes.db to /dev/
Bron,
Am 29.11.2016 um 13:26 Uhr schrieb Bron Gondwana via Info-cyrus:
No, the quota calculations are identical. It's possible that your
quota was incorrectly calculated on the source server though. A
quota -f there should correct the calculations.
unluckily it does not.
quota -f on seems no
No, the quota calculations are identical. It's possible that your quota was
incorrectly calculated on the source server though. A quota -f there should
correct the calculations.
Regards,
Bron.
On Tue, 29 Nov 2016, at 01:36, Marc Patermann via Info-cyrus wrote:
> Hi,
>
> while migrating from
