I think it would be a great idea to encourage sponsored
development to help the project move along on some
features.
If this is not something that the project admins want then
we can remove the wiki entry at:
http://www.dbmail.org/dokuwiki/doku.php#feature_requests_wish_list
Otherwise I would lik
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
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 maste
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.
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
This is great news!!
Could you maybe send me a quick overview of the major tasks
in the project? Just a punch list...
I can post them to the wiki, unless there is an existing
place to store this info for DBMail... perhaps a readme in
SVN?
No biggy on this, but it should help a bit to have a log
Wiki is good. I'm going to start a page at:
http://dbmail.org/dokuwiki/doku.php?id=sieve
Aaron
On Wed, 2005-11-16 at 15:11 -0800, Kevin Baker wrote:
> This is great news!!
>
> Could you maybe send me a quick overview of the major tasks
> in the project? Just a punch list...
>
> I can post them
I think a lot of projects call this a "bounty", rather than a
sponsorship.
If it's labeled in that manner, then people may find it if they're
looking for it.
Just my two pence, and I personally think it's a great idea, as
we've offered bounties on features that we're looking for in software
when w
Kevin Baker wrote:
> Completion of Sieve functionality, 100% compatible with
> Cyrus implementation. This would allow DBMail to be a
> complete drop-in replacement for Cyrus. I know there has
> been a good bit of work completed on this already.
> ( kevbaker at yahoo dot com $1000 )
Indeed. Now th
So,
Can we outline the requirements/steps to complete the Sieve
features set for DBMail?
- It sounds like the sievelib is ready, not sure what that
means.
- Integration into Kolab code base
- Sieve script storage system, I assume MySQL.
- Test with 2.x code base
- Test with folder routing bas
Sounds good.. I will move the funds into a paypal, so it is ready once we
work out the details.
I'm excited to move forward. I figure we can work out and post details on
the Wiki... and should probably outline quick how "Bounty" sponsored dev
will work on the project. If this works out well it mig
11 matches
Mail list logo
