The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=469
==
Reported By:menole
Assigned To:
A while back, I submitted dbmail/libsieve to Fedora-Extras for package
review and inclusion. If you're interested in see these in more
wide-spread use, or you run Fedora (*) and want to see packages more
readily available, download the srpms located in the bug and make
appropriate comments.
I
I'm not involved so I can't sponsor, but I will say kudos to you for
working on this, I will be very happy when I don't have to hand compile
DBMail for CentOS anymore.
Thanks!
Matt
Bernard Johnson wrote:
A while back, I submitted dbmail/libsieve to Fedora-Extras for package
review and
Matthew T. O'Connor wrote:
I'm not involved so I can't sponsor, but I will say kudos to you for
working on this, I will be very happy when I don't have to hand compile
DBMail for CentOS anymore.
If you're running 4.x, you might be interested in:
Ryan Butler wrote:
9853 dbmail15 0 679m 46m 660 S 0.0 9.3 5:33.60
dbmail-imapd
679 meg!
There's only about 12 people who use this on a mail store of about 3 or
4 gig. Most are running either thunderbird or evolution. The process
was started sometime on the 6th so it's
Leander Koornneef wrote:
Hi all!
I was wondering if anyone has ever tried using Sequoia (f.k.a. C-JDBC)
and Carob with DBmail to achieve high availability and/or clustering?
http://sequoia.continuent.org/
http://carob.continuent.org/
Sequoia can be used to create RAID-like database setups.
Paul J Stevens wrote:
Ryan Butler wrote:
9853 dbmail15 0 679m 46m 660 S 0.0 9.3 5:33.60
dbmail-imapd
679 meg!
There's only about 12 people who use this on a mail store of about 3 or
4 gig. Most are running either thunderbird or evolution. The process
was started sometime on
On Fri, 2006-12-08 at 04:01 -0800, Michael Dean wrote:
Ryan, which imapd are you running again?
Path: .
URL: https://svn.ic-s.nl/svn/dbmail/branches/dbmail_2_2_branch
Repository Root: https://svn.ic-s.nl/svn/dbmail
Repository UUID: 7b491191-dbf0-0310-aff6-d879d4d69008
Revision: 2361
Node Kind:
Paul J Stevens wrote:
1. install 2.2 on hostB while keeping 2.0 up and running on hostA, Both connect
to the same DBMS instance.
2. add the new tables (don't do the BYTEA conversion yet)
3. run dbmail-util -by on hostB so the new tables are filled.
4. run the BYTEA conversion on the
Rod K wrote:
Paul J Stevens wrote:
1. install 2.2 on hostB while keeping 2.0 up and running on hostA,
Both connect to the same DBMS instance.
2. add the new tables (don't do the BYTEA conversion yet)
3. run dbmail-util -by on hostB so the new tables are filled.
4. run the BYTEA
Paul J Stevens wrote:
Rod K wrote:
Paul J Stevens wrote:
1. install 2.2 on hostB while keeping 2.0 up and running on hostA,
Both connect to the same DBMS instance.
2. add the new tables (don't do the BYTEA conversion yet)
3. run dbmail-util -by on hostB so the new tables are filled.
On 8-dec-2006, at 12:59, Michael Dean wrote:
Leander Koornneef wrote:
Hi all!
I was wondering if anyone has ever tried using Sequoia (f.k.a. C-
JDBC)
and Carob with DBmail to achieve high availability and/or clustering?
http://sequoia.continuent.org/
http://carob.continuent.org/
Sequoia
Rod K wrote:
But I should still stop all services before running Step 4, correct?
To be safe: yes. If you don't and still get away with it; let us know :-)
--
Paul Stevens paul at nfg.nl
Paul J Stevens wrote:
Rod K wrote:
But I should still stop all services before running Step 4, correct?
To be safe: yes. If you don't and still get away with it; let us know :-)
LOL, I'm done being a guinea pig! Tests show that was only 4.5 hours
(bytea conversion I mean) and I
I'm in the same boat Rod, but I'm also going to upgrade my postgres. Don't
know if it
much matters, but my plan is to stop mail services, do a dump of the database,
alter
the dump so the new table will be created with bytea, then do a restore. My
calculations
are that will take 4.5 hours
On 8-dec-2006, at 17:02, Matthew O'Connor wrote:
Leander Koornneef wrote:
I partly agree with you, apart from your statement being mostly
flamebait :-)
However, riddle me this if you will:
What is the current (reasonable|viable|possible) alternative in
accomplishiing
true high availabilty
Ok, I just did the test on mysql 5.0.27. It took 73 seconds
to deliver the 1000 messages. So, it's a good bit faster
than 4.1.20's 95 seconds, but still pales in comparison to
postgres' 9 seconds. Mysql was still peaking both cpu cores
during delivery.
On Thu, 07 Dec 2006 11:23:58 -0800
Michael
17 matches
Mail list logo