Hi,
does anybody know, how ctl_cyrusdb works (how it should be used)? I've
seen ctl_cyrusdb's man pages, but there is just few notes and nothing
more.
I assume ctl_cyrusdb is used (in /etc/cyrus.conf) to generate
checkpoints of the Cyrus databases, presumably those in /var/lib/imap.
The
Some of our users have reported that they have been locked out of their
accounts.
When I examined one such occurence it seemed that one of the imapd
processes had acquired a write lock to user's seen file and doing
absolutely nothing to that seen file just holding the writelock. When this
Meta data partition:
If I want to update our cyrus installation to use metadata partition,
then how is this done.
Do I manually create the similar directory structure to the new metadata
partition as I have now in the conventional mixed data partition?
Do I manually copy over the cyrus.*
Patrick Boutilier wrote:
Bron Gondwana wrote:
snip
Not so good. Crap. And this is on 2.3.13? I don't see any changes
touching that code in the post 2.3.13 changelogs...
Correct. We have been running 2.3.13 pretty much since it was released,
2.3.12 before that, and 2.3.11 before that.
Leena Heino wrote:
Meta data partition:
If I want to update our cyrus installation to use metadata partition,
then how is this done.
Do I manually create the similar directory structure to the new metadata
partition as I have now in the conventional mixed data partition?
Do I manually
On Fri, 13 Mar 2009, Dan White wrote:
With regards to the metadata partition, there is documentation located in the
doc/install-upgrade.html file located in the source tarball release.
Thanks Dan. You are absolutely right and the metadata upgrade process was
mentioned in the
On Fri, 13 Mar 2009, Leena Heino wrote:
Though, I still could not find any information about delayed delete.
You were correct. Just update the config file to enable delayed delete,
then modify your cyr_expire event in cyrus.conf.
Andy
Cyrus Home Page:
On 12 Mar 2009, at 13:03, Dave McMurtrie wrote:
You should not need to do anything to prevent client access to a
mailbox
when it's being moved and there should never be any resulting
corruption. Cyrus locks the mailbox while it's being moved.
And any result different from the above should
Hi,
Not to interject through the pain of this.
This issue only happens when multiple users on the same domain receive
an email?
If I'm wrong, never mind.
On Mar 10, 2009, at 4:45 AM, Antony Gelberg wrote:
On 2009-03-10, Bron Gondwana br...@fastmail.fm wrote:
On Mon, Mar 09, 2009 at
