Ahhh, okay - I presumed that 'dotlock_try' required something else to
'try' after
Replacing 'dotlock_try fnctl' with just 'dotlock_try' seems to have
fixed my problem.
The idxview & logview tools are useful to learn about. Thanks.
thanks again
matt p
Timo Sirainen wrote:
On Wed, 200
On Wed, 2009-07-22 at 13:50 +1000, Matt Petoe wrote:
> 12:00:21.297181 fcntl64(9, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET,
> start=0, len=0}
>
> I have set the locks to dotlock_try followed by fcntl. The trace above
> seemed to fail with the dotlock, and proceed to fcntl?
..
> mbox_read_locks
>
> From: Mr Matthew Petoe
> Sent: 22 July 2009 23:42
> To: dovecot@dovecot.org
> Subject: RE: [Dovecot] Newbie: unable to access mailbox more than once
>
> I can fix the problem by deleting the index files for each non-compliant
>
I can fix the problem by deleting the index files for each non-compliant
mailbox. eg: /.indexes/.Sent/dovecot.index
Dovecot then recreates the index files. The ownership and permissions of the
new & deleted indexes are the same.
However, these index files soon get corrupted. I think it might b
Hello,
I'm using dovecot as a mail relay so that I can back up my providers
IMAP mail locally. I'm impressed how easy this was to set up, but I'm
having a quirk that I would like help with, if possible.
There are many weak links in my set-up chain, if you will, but I think
I've narrowed the
