Hi,
As the "new Sieve implementation" is using a "gratefully stolen
copy of
deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be
possible for the Sieve piece
1 - to be using files from dovecot directly rather than
copying&changing it (which is very bad for maintenance)
2 - to be incorporated in the hg/mercurial tree of dovecot ?
Thanks a lot in advance,
Joan
Joan wrote:> > As the "new Sieve implementation" is using a "gratefully stolen copy of > deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be > possible for the Sieve piece > 1 - to be using files from dovecot directly rather than > copying&changing it (which is very bad for maintenance) > 2 - to be incorporated in the hg/mercurial tree of dovecot ? > > Thanks a lot in advance,I guess that's why it is a FIXME. :) So, point 1 is planned, but I have no idea when Timo is going to make a common interface for this. About point 2, if you mean full integration of Sieve in the main Dovecot tree, I don't think so. I guess it will always be a separately maintained plugin. BTW, why do you bring this up? Did you encounter problems? Regards, -- Stephan Bosch stephan at rename-it.nl
Thanks What does the "patch" stand for ? I mean, do I need to apply the patch each time I update dovecot (from mercurial) ? Why not merging the 2 branches (dovecot and sieve) ? Everyone using Dovecot needs a Seive implementation I beleive. Stephan Bosch wrote:> Joan wrote: >> Hi Stephan, >> >> What is the HG url for the "ManageSieve" part ? >> > > Depends on the Dovecot version. > > Just go here for an overview: > > http://hg.rename-it.nl/ > > Regards, > > Stephan.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Jul 2009, Joan wrote:> What does the "patch" stand for ?a Mercurial queue hgrc needs the addition: [extensions] hgext.mq> I mean, do I need to apply the patch each time I update dovecot (from > mercurial) ?hg qpop --all hg pull -u hg qpush> Why not merging the 2 branches (dovecot and sieve) ? Everyone using Dovecot > needs a Seive implementation I beleive.Search the archives Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSksawnWSIuGy1ktrAQLCwAgAw07KpiWp3Ntm06D/smFNAHFN2wyxexvt OBPAL33Z/zAFtb7AYqdJlxLdcX/c+kPX3Pc4XH21qnqIKuv7xRKl4gb5Fr29N4wr MOiT7IFEo6XMzgtaS4N65TIUEHeU4mSjnA6/ehEmnYhTzgkN6JpT5V9ZKp+E916K JqOM0G1wa03uYEjv9tUVR23G+BaVUJe28KYspo8HZMkMzoiKKBmiAtB9rnHZdKkJ JCLU9R7Rq5dDVJlDiQJFN1NeyglnEfpDT6eKGyplhKHIDo0bq1YVvWq3QRE1qnGq gT2avW4uDz3kc5biA7iCqyDhCXsQXLbi1qVfU2HhwSYuc/w6cuTnzg==DmPx -----END PGP SIGNATURE-----
Joan wrote:> Thanks > > What does the "patch" stand for ? I mean, do I need to apply the > patch each time I update dovecot (from mercurial) ?The patch is needed to let Dovecot know of the existence of the ManageSieve protocol. Read the wiki for more info on this patch and how to apply it for Mercurial repositories: http://wiki.dovecot.org/ManageSieve> Why not merging the 2 branches (dovecot and sieve) ? Everyone using > Dovecot needs a Seive implementation I beleive. >With the advent of Dovecot v2.0, the patch is gone. However, the Sieve/ManageSieve support will remain a separate package. Regards, Stephan.
Ok, I made it happen. Now, 2 questions: * I have a generic script in the Virtual Mailboxes directory (to handle spam, virus, etc...). How the general script and the one defined by the user will compete/interact ? * How to convert Thunderbird filters to Sieve filters ? Thanks JM Stephan Bosch wrote:> Joan wrote: >> Thanks >> >> What does the "patch" stand for ? I mean, do I need to apply the >> patch each time I update dovecot (from mercurial) ? > The patch is needed to let Dovecot know of the existence of the > ManageSieve protocol. Read the wiki for more info on this patch and how > to apply it for Mercurial repositories: > > http://wiki.dovecot.org/ManageSieve > >> Why not merging the 2 branches (dovecot and sieve) ? Everyone using >> Dovecot needs a Seive implementation I beleive. >> > With the advent of Dovecot v2.0, the patch is gone. However, the > Sieve/ManageSieve support will remain a separate package. > > Regards, > > Stephan.