[Dovecot] Running dovecot-lda
Hi,
I'm planning on setting up dovecot with dovecot-lda, for sieve support. What does the list have to say about versions to use? I prefer stability over features but sieve has to be there.
Does anybody use the combination dovecot 1.0 alpha5 and dovecot-lda 0.1 with success or would you recommend running -lda from CVS? If so, is there any point in time that's better than another? And, will dovecot 1.0 alpha5 do for -lda from CVS?
Finally, are there any release plans for dovecot-lda that can be shared?
Thanks,
Linus
Hi,
On 4/01/2006 1:36 p.m., Linus Nordberg wrote:
Hi,
I'm planning on setting up dovecot with dovecot-lda, for sieve support. What does the list have to say about versions to use? I prefer stability over features but sieve has to be there.
There is only one version of dovecot-lda; that in CVS. There is no official/final release of it yet.
Does anybody use the combination dovecot 1.0 alpha5 and dovecot-lda 0.1 with success or would you recommend running -lda from CVS? If so,
I'm usually synced up to both in CVS (non critical machine) and at the moment it works OK. I doubt you'd have problems mixing dovecot-lda CVS with anything remotely recent but you should ideally run latest alpha release (or CVS if you track the changes) of dovecot also.
is there any point in time that's better than another? And, will dovecot 1.0 alpha5 do for -lda from CVS?
The deliver binary in the main dovecot tree has been deprecated, going by recent commit messages to CVS, and is no longer compilable in the dovecot tree. You will need to pull the lda branch separately from the CVS server and build it alongside dovecot, and configure the lda in dovecot.conf.
Btw I'm yet to see a good reason why you wouldn't use the lda unless you want to maintain procmail recipes as is or some other unique delivery mechanism.
I'd say going by the changes in CVS, it is only a matter of short time before the deliver code is pulled from dovecot, and the once-separated super-sieve-ehnahced lda merged in to become part of the core package.
Finally, are there any release plans for dovecot-lda that can be shared?
It seems pretty stable now, so only Timo can reveal that ;-)
I haven't got any outstanding issues with the LDA, however I've a handful on the core dovecot right now which I have worked around one way or another.
Have you looked at http://wiki.dovecot.org/ and through the information on there?
reuben
On Wed, 2006-01-04 at 17:15 +1300, Reuben Farrelly wrote:
Does anybody use the combination dovecot 1.0 alpha5 and dovecot-lda 0.1 with success or would you recommend running -lda from CVS? If so,
I'm usually synced up to both in CVS (non critical machine) and at the moment it works OK. I doubt you'd have problems mixing dovecot-lda CVS with anything remotely recent but you should ideally run latest alpha release (or CVS if you track the changes) of dovecot also.
Current dovecot-lda can use dovecot.conf nowadays, and requires a "protocol lda" section in dovecot.conf. That however gives config parsing error with anything but latest Dovecot CVS.. You could of course make dovecot-lda use a separate config file.
I'd say going by the changes in CVS, it is only a matter of short time before the deliver code is pulled from dovecot, and the once-separated super-sieve-ehnahced lda merged in to become part of the core package.
Not really. I'd rather see some other Sieve implementation used by Dovecot-LDA, but there just doesn't seem to be any easy way to use others than the Cyrus Sieve. I'll at some point merge the two different LDAs and make some kind of easy way to plug in Sieve code, but the Sieve code will still stay as separate package..
Timo Sirainen tss@iki.fi wrote Wed, 04 Jan 2006 12:23:59 +0200:
| On Wed, 2006-01-04 at 17:15 +1300, Reuben Farrelly wrote:
| > > Does anybody use the combination dovecot 1.0 alpha5 and dovecot-lda
| > > 0.1 with success or would you recommend running -lda from CVS? If so,
| >
| > I'm usually synced up to both in CVS (non critical machine) and at the moment it
| > works OK. I doubt you'd have problems mixing dovecot-lda CVS with anything
| > remotely recent but you should ideally run latest alpha release (or CVS if you
| > track the changes) of dovecot also.
|
| Current dovecot-lda can use dovecot.conf nowadays, and requires a
| "protocol lda" section in dovecot.conf. That however gives config
| parsing error with anything but latest Dovecot CVS.. You could of course
| make dovecot-lda use a separate config file.
Thanks, both of you, for good info. I'll go for current CVS for both dovecot and -lda.
(Attached is a small patch for compiling dovecot-lda on systems with com_err.h directly in /usr/include. Should patches go elsewhere?)
-- Linus
participants (3)
-
Linus Nordberg
-
Reuben Farrelly
-
Timo Sirainen