Most definitely!

Since your last email, I've got DBMail 2.1 SVN to compile cleanly with
libSieve 2.1.7. It doesn't actually work, because the callbacks are just
the skeleton ones from libSieve. It means that ./configure --with-sieve
works, and builds dbmail-sievecmd and the dbmail-timsieved daemon.

Anybody who wants to jump in on this, I'm more than happy to help
coordinate work on this project.

Aaron


On Wed, 2005-11-16 at 13:38 -0800, Kevin Baker wrote:
> Hi Aaron,
> 
> Is the sponsored development (feature bounty) for Sieve
> support something you are interested in?
> 
> We are doing some infrastructure planning for the next
> couple months. Either way is fine, but if this is something
> you can work on I'd like to consider moving over to DBMail
> in production.
> 
> 
> Thanks,
> 
> Kevin
> 
> 
> 
> --- Kevin Baker <[EMAIL PROTECTED]> wrote:
> 
> > 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
> > >
> > >
> > >
> > >
> > 
> > 
> > 
> > _______________________________________________
> > Dbmail-dev mailing list
> > [email protected]
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> > 
> 
> 
> Kevin Baker
> Mission Vi Inc.
> [EMAIL PROTECTED]
> 858.454.5532
> 
> 
>               
> __________________________________ 
> Yahoo! FareChase: Search multiple travel sites in one click.
> http://farechase.yahoo.com
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Reply via email to