Hi,
We run a traditional murder with Cyrus 2.3.12p2 - 2 frontend, 2
backend, and a mupdate server.
Whenever we migrate mailboxes all the mailboxes for the domain are
moved at the same time, and there's a high chance that the quota usage
will get messed up and mailboxes will have more than 1
On 16 Nov 2010, at 13:38, Adam Tauno Williams wrote:
>
> Our largest quota's a 4GB; without any issues.
>
> I think the issue you will encounter first is clients will start to
> fall
> down when folders exceed a 'reasonable' number of messages. Common
> IMAP
> clients I've seen start to exhib
r_dbtool.
This was 2.4.6 -> 2.3.12 so maybe there's some discrepancy in what
2.4.6 sends vs what 2.3 and 2.4 expect?
Simon
--
Simon Amor
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
versions (convert
mailboxes.db and others to skiplist format first). I've successfully migrated
2.2.x (CentOS4) to 2.4.8 using this method.
Simon
--
Simon Amor
si...@leaky.org
http://www.leaky.org/
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
On 9 Jul 2013, at 22:20, Shawn Winnington-Ball wrote:
>
>> You can force a backend to push all of its mailboxes to the mupdate master
>> by running "ctl_mboxlist -m" on the backend. If you're not 100% sure
>> whether you want to push every mailbox before you know what state things
>> are in, you
er
32268 ?Ss 0:07 /usr/lib/cyrus-imapd/cyrus-master -d
The -f argument to reconstruct according to the man page:
Examine the filesystem underneath mailbox, adding all directories with a
cyrus.header found there as new mailboxes. Useful for restoring mailboxes from
backups.
Regards,
On 10 Mar 2014, at 20:31, Marcus Schopen wrote:
>
> When deleting a single message from Inbox or a subfolder these message
> are not moved into a DELETED structure and keep staying at their
> originally place on filesystem. Those messages are definitely delete. I
> can't see them in my imap clie
