On 9/20/2010 8:59 AM, Marc Patermann wrote:
And still, if someone asks a mailing list (not here certainly) how to
start with IMAPd, many people shout, to go with dovecot and not using
Cyrus.
Hi -
A little late to this thread, but here are a couple of modest
observations:
1.
I have
On Wed, Sep 22, 2010 at 07:50:25AM +0200, Simon Matter wrote:
Debian is still stuck on 2.2 and there seems to be no progress in that
area.
The main problem they apparently have, is the migration path for the
various
DB files from 2.2 to 2.3.
(The 2.3 version itself works fine as
Am 21.09.2010 23:15, schrieb Jeffrey T Eaton:
Debian is still stuck on 2.2 and there seems to be no progress in that area.
The main problem they apparently have, is the migration path for the various
DB files from 2.2 to 2.3.
(The 2.3 version itself works fine as .deb packages)
What
On Wed, Sep 22, 2010 at 08:02:35AM +0200, Simon Matter wrote:
Documentation is one thing, and dependencies like BDB another. But there
is something else I guess, for servers which are not dedicated mail
server, it would be really nice if one could install Cyrus and it just
works for every user
--On 22. September 2010 16:10:15 +1000 Bron Gondwana br...@fastmail.fm
wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is necessary, and
(b) doing the upgrade.
I wouldn't exactly call myself an expert, but I
On Wed, 22 Sep 2010 09:12 +0200, Sebastian Hagedorn haged...@uni-koeln.de
wrote:
--On 22. September 2010 16:10:15 +1000 Bron Gondwana br...@fastmail.fm
wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is
On Wednesday 22 September 2010 09:01:33 Bron Gondwana wrote:
On Wed, Sep 22, 2010 at 08:02:35AM +0200, Simon Matter wrote:
snipped
Bron ( really trying to make Cyrus newbie-friendly as well as advanced-site
friendly. I also want auto-recompilation of sieve scripts, and
Adam Tauno Williams wrote:
On Tue, 2010-09-21 at 12:25 +0200, Syren Baran wrote:
Am Dienstag, den 21.09.2010, 11:48 +0200 schrieb André Schild:
Am 21.09.2010 11:35, schrieb Simon Matter:
I don't know, where this bad karma is coming from - I'm still happy
with
I guess it's
On Wed, Sep 22, 2010 at 10:13:20AM +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 09:01:33 Bron Gondwana wrote:
On Wed, Sep 22, 2010 at 08:02:35AM +0200, Simon Matter wrote:
snipped
Bron ( really trying to make Cyrus newbie-friendly as well as advanced-site
friendly.
given the issues with BDB. Is it worth embedding a copy of
BDB into the Cyrus distribution rather than using the OS one? I
know it's generally considered bad taste, but it sure makes
keeping in sync easier!
IMHO, yes, most certainly. Cyrus is a large and complex system, and its
On Sep 22, 2010, at 1:50 AM, Simon Matter wrote:
Debian is still stuck on 2.2 and there seems to be no progress in that
area.
The main problem they apparently have, is the migration path for the
various
DB files from 2.2 to 2.3.
(The 2.3 version itself works fine as .deb packages)
--On 22. September 2010 07:47:26 -0400 Jeffrey T Eaton jea...@cmu.edu
wrote:
All of that said, I believe that, in general, you can safely upgrade BDB.
If you have a Cyrus installation using BDB X, you can drop in a new Cyrus
using BDB Y, as long as everything is shut down in between. You
On Wed, Sep 22, 2010 at 04:43:23PM +0530, Shuvam Misra wrote:
I'm open to criticism, but I strongly feel Cyrus should carry its own
version of some of these critical system libraries, specially those ones
which have caused so much compatibility grief in its history. I know this
is considered
On Sep 22, 2010, at 7:57 AM, Sebastian Hagedorn wrote:
--On 22. September 2010 07:47:26 -0400 Jeffrey T Eaton jea...@cmu.edu wrote:
All of that said, I believe that, in general, you can safely upgrade BDB.
If you have a Cyrus installation using BDB X, you can drop in a new Cyrus
using BDB
On Sep 22, 2010, at 7:57 AM, Sebastian Hagedorn wrote:
--On 22. September 2010 07:47:26 -0400 Jeffrey T Eaton jea...@cmu.edu
wrote:
All of that said, I believe that, in general, you can safely upgrade
BDB.
If you have a Cyrus installation using BDB X, you can drop in a new
Cyrus
using
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here, but
And, as Bron has said, there's something wrong with the way Cyrus uses BDB.
I've never been able to understand BDB well enough to figure it out
myself, nor have I ever found
On Wed, 2010-09-22 at 14:44 +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here, but
And, as Bron has said, there's something wrong with the way Cyrus uses BDB.
I've never been able to understand BDB
On Wed, Sep 22, 2010 at 04:43:23PM +0530, Shuvam Misra wrote:
I'm open to criticism, but I strongly feel Cyrus should carry its own
version of some of these critical system libraries, specially those ones
which have caused so much compatibility grief in its history. I know
this
is considered
On 22/09/2010, at 22:17, Adam Tauno Williams wrote:
On Wed, 2010-09-22 at 14:44 +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here, but
And, as Bron has said, there's something wrong with the way Cyrus
On Wed, 2010-09-22 at 14:44 +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here, but
And, as Bron has said, there's something wrong with the way Cyrus uses
BDB.
I've never been able to understand BDB
On Wed, Sep 22, 2010 at 10:27:11PM +0930, Daniel O'Connor wrote:
On 22/09/2010, at 22:17, Adam Tauno Williams wrote:
On Wed, 2010-09-22 at 14:44 +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here,
On 22/09/2010, at 22:33, Kenneth Marshall wrote:
On a bad shutdown it requires admin intervention very frequently which is
pretty tedious.
And yes, upgrading it is also a PITA.
That is why we moved to skiplist. The server would require manual
intervention to even restart after certain
On Wed, Sep 22, 2010 at 10:48:49PM +0930, Daniel O'Connor wrote:
On 22/09/2010, at 22:33, Kenneth Marshall wrote:
On a bad shutdown it requires admin intervention very frequently which is
pretty tedious.
And yes, upgrading it is also a PITA.
That is why we moved to skiplist.
On Wed, 2010-09-22 at 15:04 +0200, Simon Matter wrote:
On Wed, 2010-09-22 at 14:44 +0200, J. Roeleveld wrote:
On Wednesday 22 September 2010 13:47:26 Jeffrey T Eaton wrote:
snipped
I am probably missing some info here, but
And, as Bron has said, there's something wrong with the way
Just so you know, the policies of most Linux distributions forbid this
kind of bundling, so unless it's easily disabled (and preferably
defaults to using system libraries) the distributions will just have to
patch it back out again. For example, here's the Fedora policy:
On Wednesday 22 September 2010 15:29:20 Kenneth Marshall wrote:
On Wed, Sep 22, 2010 at 10:48:49PM +0930, Daniel O'Connor wrote:
On 22/09/2010, at 22:33, Kenneth Marshall wrote:
On a bad shutdown it requires admin intervention very frequently which
is pretty tedious.
And yes,
On Wednesday 22 September 2010 15:29:20 Kenneth Marshall wrote:
On Wed, Sep 22, 2010 at 10:48:49PM +0930, Daniel O'Connor wrote:
On 22/09/2010, at 22:33, Kenneth Marshall wrote:
On a bad shutdown it requires admin intervention very frequently
which
is pretty tedious.
And yes,
For me it would be very interesting a option to save cyrus tables
in a traditional database. ( mysql, postgresql, etc... )
Zinato
On Wed, Sep 22, 2010 at 11:06 AM, Simon Matter simon.mat...@invoca.ch wrote:
On Wednesday 22 September 2010 15:29:20 Kenneth Marshall wrote:
On Wed, Sep 22,
On 09/22/2010 10:17 AM, Lucas Zinato Carraro wrote:
For me it would be very interesting a option to save cyrus tables
in a traditional database. ( mysql, postgresql, etc... )
In 2.3.13 (I think) and newer, there is the option of using an SQL
backend. It hasn't been widely used and tested
Am 22.09.2010 16:17, schrieb Lucas Zinato Carraro:
For me it would be very interesting a option to save cyrus tables
in a traditional database. ( mysql, postgresql, etc... )
Beside interesting what would you get for a real benefit from this ?
They are ver verly likely to be slower.
André
On 09/22/2010 10:52 AM, André Schild wrote:
Am 22.09.2010 16:17, schrieb Lucas Zinato Carraro:
For me it would be very interesting a option to save cyrus tables
in a traditional database. ( mysql, postgresql, etc... )
Beside interesting what would you get for a real benefit from this
We wanted to use it for the user_deny database so we could insert a row
into one database table that every host has access to. This way we
didn't need to come up with a way to update the local user_deny across
each frontend server.
Such database provides the same benefit to the tlscache
On Wed, 22 Sep 2010, Bron Gondwana wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is necessary, and
(b) doing the upgrade.
All I know is that there used to be an API call to upgrade the db
environment, which
Kolab Systems is thinking of such SQL databases for integration purposes, where
the performance penalty now lies within having to use the IMAP protocol to gain
access to the underlying metadata (seen status, message indexes) in distributed
groupware environments where Cyrus itself is not the
Hi,
Kolab Systems is thinking of such SQL databases for integration purposes,
where the performance penalty now lies within having to use the IMAP
protocol to gain access to the underlying metadata (seen status, message
indexes) in distributed groupware environments where Cyrus itself is
Dear list!
We are running a Cyrus Murder configuration.
In the mailboxlist (which I can get using ctl_mboxlist, I can see on which
backend each mailbox resides physically.
Is there any way to extract that information through the IMAP protocol?
What I mean is, I can issue a command:
list Mail
On Wed, 22 Sep 2010, Torsten Schlabach wrote:
Dear list!
We are running a Cyrus Murder configuration.
In the mailboxlist (which I can get using ctl_mboxlist, I can see on
which backend each mailbox resides physically.
Is there any way to extract that information through the IMAP
The big downside to using an SQL database is the enormous temptation to
point all the Cyrus servers at the same Database server and lose the
redundancy and scalability inherent in a multi node or Murder setup.
But the SQL world has this figured out, at least for reads. For
situations where
On 22 Sep 2010, at 10:46, Dave McMurtrie wrote:
Considering the state of Cyrus' interoperability with BDB and all the
recent fixes to skiplist, would it make sense to at least not make BDB a
default backend from now on?
Yes, and sane defaults was to be one of the themes of the 2.4 release.
On Wed, Sep 22, 2010 at 04:10:15PM +1000, Bron Gondwana wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is necessary, and
(b) doing the upgrade.
It was quite some time ago I last upgraded a Cyrus instance, but
On Wed, Sep 22, 2010 at 11:24:04PM +0200, Gabor Gombas wrote:
On Wed, Sep 22, 2010 at 04:10:15PM +1000, Bron Gondwana wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is necessary, and
(b) doing the upgrade.
given the issues with BDB. Is it worth embedding a copy of
BDB into the Cyrus distribution rather than using the OS one? I
That way lies madness.
BDB is one of those things where arcane blackmagic skills are needed to keep
it working on all arches. It uses scary crap to be fast
On Thu, 23 Sep 2010, Shuvam Misra wrote:
given the issues with BDB. Is it worth embedding a copy of
BDB into the Cyrus distribution rather than using the OS one? I
That way lies madness.
BDB is one of those things where arcane blackmagic skills are needed to keep
it
Kolab Systems is thinking of such SQL databases for integration
purposes, where the performance penalty now lies within having to use the
IMAP protocol to gain access to the underlying metadata (seen status,
message indexes) in distributed groupware environments where Cyrus
itself is not the
On Wed, Sep 22, 2010 at 04:10:15PM +1000, Bron Gondwana wrote:
Now - BDB database SHOULD be upgradable. I want to find a BDB expert
to help me with that - (a) detecting that an upgrade is necessary, and
(b) doing the upgrade.
It was quite some time ago I last upgraded a Cyrus instance, but
45 matches
Mail list logo
