Yes... here is my exact goal. - Replace Cyrus with DBMail on a Kolab installation - Inteagrate DBMail with Kolab LDAP user schema - test Sieve integration with Kolab admin vacation message stuff - Setup an identical hot failover server with same configuration - Setup LDAP replication between master and slave secondary failover machine - Setup MySQL replication between master and slave secondary failvoer machine. - this will be a two machine cluster, on main on hot failover - Test a failover
Requirements: - Its ok to loose some messages if the master fails - Secondary machine should be pretty much in sync, w/in 5 mins or so - No message corruption - Simple mailbox migration to second mail cluster to scale if we have to add a lot more users. Pretty sure if sieve is working in DBMail then all the above should work. Don't exect this list to focus on any of hte kolab stuff, but the ldap integration and Sieve support would be great. Have you done a hot failover solution ever for DBMail. Just want message replicated. The idea being that if I have my primary fail I can just swith DNS to the secondary and go to town. Thanks for Aaron, Kevin > On Sun, 2005-10-30 at 21:30 -0800, Kevin Baker wrote: > >> BTW: I included integration into "Kolab" as a requirement for me. Oops >> just another project I work a lot with. I meant integration with >> *DBMail* >> ;) > > Is your goal to run a Kolab server with DBMail instead of Cyrus? We're > only missing Sieve, I think. DBMail supports shared folders and I set up > SASL on my server to pull from DBMail's database in MySQL. I should post > that config on the Wiki... > > Aaro > > > >
