On pe, 2010-05-28 at 16:00 -0500, Stan Hoeppner wrote:
If non-Dovecot MUAs modify mbox simultaneously (except appends by MDA are ok), Dovecot might not notice those changes immediately and it might log some errors sometimes.
So it's the same caveat as with mbox_dirty_syncs = yes. If the caveats are the same, why do both settings exist, given that mbox_very_dirty_syncs=yes yields superior performance? Is there more potential danger with mbox_very_dirty_syncs? That was the impression I had, thus why I was using the "milder" setting.
With mbox_dirty_syncs it eventually notices the changes the next time the mailbox is SELECTed. But that's of course slow. The default behavior is similar to UW-IMAP's, that's the main reason the very dirty syncs isn't enabled by default.