-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Stone wrote:
>> Yes, that's correct -- however on trunk I'm improving this situation so
>> that keywords are not strewn all over the codebase. This weekend, (I
>> promise!) I'm going to get the libsieve trunk into better shape and
>> start identifying the work needed to support RFC 5228 - 5235:
> 
>> 5228 Sieve: An Email Filtering Language
>> 5229 Sieve Email Filtering: Variables Extension
>> 5230 Sieve Email Filtering: Vacation Extension
>> 5231 Sieve Email Filtering: Relational Extension
>> 5232 Sieve Email Filtering: Imap4flags Extension
>> 5233 Sieve Email Filtering: Subaddress Extension
>> 5235 Sieve Email Filtering: Spamtest and Virustest Extensions
> 
>> (The consistent naming was one of my contributions ;-)
> 
>> And also 3894, copy without side effects (add :copy to fileinto and
>> redirect, which cause the implicit keep to remain in effect, should be
>> very simple to implement)
> 
>> Thank you for your interest in digging into this work!
> 
>> Aaron
> 
Aaron
the patch I did this morning is probably not usable, but no problem, it
meant I learnt it bit about how things are structured in libsieve.
When you've done the restructuring and identified some pieces of work
that need doing, just drop me a line. I'll be glad to help.
thanks,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFHwGz1d4I3jTtt9EIRAqSgAJ991qcEIh/fLF92kCZInr64LbYGqACaAubY
TwYj9wega0DhI8CKhLhilCc=
=nt0+
-----END PGP SIGNATURE-----
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Reply via email to