--syncinternaldates stopped working at imapsync 1.200 (current is
1.204), as a side effect of the append_string-append_file change
suggested by John Capo and Florin Andrei earlier in this thread, on Dec
26, 2006. That change was made to avoid memory exhaustion, see
A bunch of people already pointed out unexpunge, so I'll point out
that the delayed expunge / unexpunge functionality doesn't help if
the user deletes a whole folder. See:
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2871
for the problem report and a patch for a proposed solution.
On 19.01.2007, at 01:02, Blake Hudson wrote:
I know I've seen it before, but I've been having a hard time finding a
good comparison of the different db types supported by cyrus and their
respective strengths/weaknesses. Does anyone have a link they could
share?
There's a short information
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2871
I also found out that delayed_expunge doesn't help if a whole folder got
deleted. So if something like your proposed solution gets included that
would really be a very nice feature.
Agreed. This would also allow for complete backups of all
I already mailed the author of imapsync about that some days ago but
without having an idea how to fix it. I also checked Mail::IMAPClient and
found that it lacked the functionality needed here but it seems
Mail::IMAPClient isn't maintained anymore (at least there is no
development for long time
so I wonder, will skiplist be a better choice? obviously running
quota(8) will be a very cheap operation, but I'm worried about
contention on the quota database during delivery etc. (these users are
for the most part not actively using the system -- they get less than
one message per day
Rob Mueller wrote:
so I wonder, will skiplist be a better choice? obviously running
quota(8) will be a very cheap operation, but I'm worried about
contention on the quota database during delivery etc. (these users are
for the most part not actively using the system -- they get less than
one
On Fri, 2007-01-19 at 21:58 +1100, Rob Mueller wrote:
What filesystem are you using? Have you considered trying reiserfs with
tails enabled. It's quite impressive how little disk space it actually uses
(don't believe du output). We used to use NVRAM cards, and even with 100,000
users, it
On Fri, 2007-01-19 at 07:49 -0500, Ken Murchison wrote:
Rob Mueller wrote:
The problem I saw was that accessing a skiplist db involves locking the
entire file I believe. This felt like a huge point of contention,
especially since every email delivered would lock it. I never did end up
Or things get mangled and people end up over quota.
(from my Treo)
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
-Original Message-
From: Kjetil Torgrim Homme [EMAIL PROTECTED]
To: Ken Murchison [EMAIL PROTECTED]
Cc: Rob Mueller
Thanks, this is exactly what I was looking for. Now, can someone please
explain what the annotations and pts databases are used for?
I've had some locking issues with the deliver.db and would like to
switch all of the berkeley databases over to skiplist. Once this is
completed will there still be
Gary Mills wrote:
On Thu, Jan 04, 2007 at 07:47:54AM -0500, Ken Murchison wrote:
Gary Mills wrote:
On Wed, Jan 03, 2007 at 08:18:15AM -0500, Ken Murchison wrote:
Gary Mills wrote:
Can I use the old server as both a front end and one of the back ends
for a murder configuration, with the new
On 18 Jan 2007, at 20:16, Gary Mills wrote:
Is there any documentation on how to configure and manage a unified
Murder?
See the man page for imapd.conf:
mupdate_config: standard
The configuration of the mupdate servers in the Cyrus
Murder. The
standard config
On 19 Jan 2007, at 05:50, Rob Mueller wrote:
I know David Carter implemented a patch for this in 2.2. I'm not
sure if Wesley's patch is related to it or a completely separate
implementation.
Completely separate, tho my is based on comment from David suggesting
how he would do it if he
14 matches
Mail list logo
