Thanks Timo,
Indeed in my case INBOXes are mbox format and are only accessed bydovecot and procmail. Procmail only appends new mails onto mboxes. So as you say, mbox_very_dirty_syncs will avoid full index rebuilding.
I eager to use dovecot 1.x stable and to migrate into indexedMaildir. Right now on production servers I use UW-IMAP, and I feel very uncomfortable about it. I have resorted to multi-way disk mirroring and stripping to handle the UW disk load, which causes average 30MB/second rates sustained throughout working hours, with frequent peaks of 80MB/second.
I use dovecot 0.99.12.1 for selected users, and it works ok, but Iknow it will not be developed further, so I don't intend to deploy it further.
Keep up the very good work!
Apostolis Papayanakis apap@ccf.auth.gr, 2310-998416
On Mon, 10 Jan 2005, Timo Sirainen wrote:
On Mon, 2005-01-10 at 00:36 +0200, Apostolos Papayanakis wrote:
I hope there will soon be a plain delivering tool for dovecot 1.x. I could use it right away as the delivering step with procmail, which would run it under recipient's uid and context (all recipients are real unix users in my case).
I'll try to get it done soon.
Without a local delivery agent, dovecot will always seem slower than its rivals when opening INBOXes with new mails, especially large ones, because of index creation delays.
So you're using mboxes? If nothing else than Dovecot is modifying mboxes (adding mail is fine), you could use:
mbox_very_dirty_syncs = yes
Then the mbox is re-read only when absolutely necessary (something else has modified the mbox and mails aren't where they're expected). I've been using it for a few months (or whenever it was I added that feature), works fine.