Re: [Dovecot] LDA vs maildrop... LDA *and* maildrop?

>> 1. we use a lot of maildrop "features" that are impossible in >> sieve > > We're calling deliver from maildropc Ah, so this is actually sane enough of an idea that someone really uses it?  Is the performance reasonable?  Bounces or deferred mail all work as expected?  What syntax did you

Re: [Dovecot] LDA vs maildrop... LDA *and* maildrop?

> We're considering a move from Courier to Dovecot.  So far, looks like > it's not too bad, but the most challenging obstacle is what to do about > our local delivery.  Factors: > > 1. we use a lot of maildrop "features" that are impossible in sieve > > without piping to an external program (w

[Dovecot] LDA vs maildrop... LDA *and* maildrop?

We're considering a move from Courier to Dovecot.  So far, looks like it's not too bad, but the most challenging obstacle is what to do about our local delivery.  Factors: 1. we use a lot of maildrop "features" that are impossible in sieve without piping to an external program (would rather not

Re: [Dovecot] Manual manipulation of Sieve files

Thanks for the reply -- >> We have some scripts that take care of some tasks when creating new email > accounts, such as creating some default mail filter rules. >> >> I know Sieve scripts are plain text files, but need to be compiled for >> use.  I see that you can use seivec to compile sc

Re: [Dovecot] Dovecot performance under high load (vs. Courier)

>>> Oh, and of course it also depends on Dovecot configuration :) >>> Authentication >>> cache is needed and login processes must be in high performance mode. >> >> I.e., I think: >> >> http://wiki2.dovecot.org/LoginProcess >> http://wiki2.dovecot.org/Authentication/Caching > > Yes. > >

Re: [Dovecot] Dovecot performance under high load (vs. Courier)

> Oh, and of course it also depends on Dovecot configuration :) Authentication > cache is needed and login processes must be in high performance mode. I.e., I think: http://wiki2.dovecot.org/LoginProcess http://wiki2.dovecot.org/Authentication/Caching > There is > still the extra work of fork

Re: [Dovecot] Dovecot performance under high load (vs. Courier)

Thank you very much for the fast reply. >> We are building a new system that will support a large number of users >> (high volume, high concurrent usage, etc).  We have played with Dovecot, but >> in >> most serious applications we have traditionally used Courier IMAP.  It's my >> (lay) unde

[Dovecot] Manual manipulation of Sieve files

We have some scripts that take care of some tasks when creating new email accounts, such as creating some default mail filter rules. I know Sieve scripts are plain text files, but need to be compiled for use.  I see that you can use seivec to compile scripts manually, which can help me create .

[Dovecot] Dovecot performance under high load (vs. Courier)

Hi, We are building a new system that will support a large number of users (high volume, high concurrent usage, etc).  We have played with Dovecot, but in most serious applications we have traditionally used Courier IMAP.  It's my (lay) understanding that with indexing and perhaps other things

Re: [Dovecot] Running 1.x and 2. x on same machine

> > When building from source, is it possible to use "make install" to switch > > between version 1.x and 2.x on the same machine (just for testing)? > > I do that all the time. > > > Do both versions install the same binaries? > > No, but as long as you don't use the other one's extra

[Dovecot] Running 1.x and 2. x on same machine

Hello, When building from source, is it possible to use "make install" to switch between version 1.x and 2.x on the same machine (just for testing)? Do both versions install the same binaries? Is configuration from 2.x backward compatible with 1.x? (so we can have the newest configuration fil