Hi, What exactly do you mean with "deliver preps the index"? Dovecot itself preps/creates/alters the index, when retrieving mail; right? Or are you (probably) saying this is one more benefit of using 'deliver'.
Anyone know of any 'deliver'/(dovecot) stresstests with regards to forking and threading of the deliver binary? Cheers, Jan -----Oorspronkelijk bericht----- Van: Gabriel Millerd [mailto:[EMAIL PROTECTED] Verzonden: zaterdag 23 februari 2008 4:01 Aan: Jan van den Berg Onderwerp: Re: [Dovecot] Dovecot Sieve scalability On Fri, Feb 22, 2008 at 2:55 AM, Jan van den Berg <[EMAIL PROTECTED]> wrote: > > The Dovecot/Sieve implementation is functional but not very elegant or > robust. But this can be explained because Dovecot is build for > _retrieving_ mail (imap/pop) and _not_ delivering mail. > Deliver preps the index, makes retrieving email faster. More so for the average disorganized INBOX in my only folder customers. Sieve makes a lot of things smoother for users, the customer. Especially if they expect server side rules. Obviously the rules that drop each message into a Backups or forward messages to other hosts take up what they take up. My sievec files have ancient mtimes. They are definitely not recompiled upon receiving each email. > Any thoughts on this? Are there people out there with large > Dovecot+Sieve implementations (100k+ users). Are there benchmarks > available; how well does it perform under heavy load (mails/sec)? > Depends entirely on the sieve rules in place. -- Gabriel Millerd
