I've got the new libSieve API documented at http://libsieve.sf.net/  and
CVS is now up to date with my working tree. I'll be snapping out the 2.1.7
release later this week. Before I call it 2.2.0 stable, I want to write a
testsuite to ensure that libSieve is sticking to the latest Sieve RFC's
and drafts.

Now, a quick question: Paul, do you intend to make the 2.1 series
multithreaded? See, flex is still stuck in single-thread land... so we
should hold off on multithreading until flex gets fixed. Or I have to
rewrite libSieve's lexer and parser in something else (ugh).

DParser looks really neat. We might consider using that for the IMAP
parser in DBMail.

As far as Sieve support goes, I'm going to rewrite the old 2.0 series
Sieve interface to use to the new API, and then forward port it into 2.1.
If anybody's interested in helping (I ask this every few months and expect
different answers? :-P) just drop me a line!

Aaron

Reply via email to