Re: [Dovecot] mbox sync/lock issue, rc28 and later

On 6.4.2007, at 20.36, Timo Sirainen wrote:

I guess this has something to do with NFS attribute caching then.
For now you could disable the check by changing
mbox_sync_file_is_ext_modified() to just contain "return FALSE;" in
mbox-sync.c.

Hmm. Wonder if I should add a new setting for this or just disable
the check completely for v1.0.. The reason why I added it in the
first place was because I wanted to know if some mbox problems were
caused by locking problems or real bugs in Dovecot. If the settings
are correct it's a bit useless to do this check.

This makes it give the error only if it notices a problem in the mbox
file: http://dovecot.org/list/dovecot-cvs/2007-April/008615.html

So I guess I'll do rc31 still this weekend. :)