On Fri, 2006-04-21 at 15:38 +0100, Obantec Support wrote:

sorry to jump on this conversation but this is a pain for me on FC3 with 1.0 stable. are you saying that the conf line for lock files mbox format under /var/spool/mail/%u should only read

mbox_read_locks = fcntl mbox_write_locks = fcntl

i have

mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

No, having the dotlock files is safer. But *IF* everything that is writing to mboxes uses fcntl locking, you don't necessarily need dotlocks. That means mostly your MDA, but also anything else that touches the mboxes.

On Fri, 2006-04-21 at 16:06 +0100, Obantec Support wrote:

----- Original Message ----- From: "Timo Sirainen" <tss@iki.fi> To: "Obantec Support" <support@obantec.net> Cc: <dovecot@dovecot.org> Sent: Friday, April 21, 2006 3:54 PM Subject: Re: [Dovecot] LOCK FILE

my MDA is procmail3.22 which returns in responce to procmail -v

Locking strategies: dotlocking, fcntl()

So, in that case it should be safe not to use dotlocking with Dovecot. But if your mboxes start getting corrupted change it back. :)

On Sat, 2006-04-22 at 12:12 +0100, Obantec Support wrote:

changing the locking strategies to

mbox_read_locks = fcntl mbox_write_locks = fcntl

has not improved the situation as 1 more user is now stuck in the username.lock problem.

is it just me suffering with mbox locking on random users? (its only 1 or 2 over 200+ POP3 accounts) but i need to resolve it.

If you have such settings, then it's not Dovecot creating or looking at the .lock files. Must be your procmail or something else (crashing maybe while delivering the mail and leaving the .lock file lying there?).

On Mon, 2006-04-24 at 11:06 +0100, Obantec Support wrote:

----- Original Message ----- From: "Timo Sirainen" <tss@iki.fi> To: "Obantec Support" <support@obantec.net> Cc: <dovecot@dovecot.org> Sent: Monday, April 24, 2006 10:46 AM Subject: Re: [Dovecot] LOCK FILE

So how do i stop dovecot using the locks.

If you really did configure the dotlocks away, Dovecot is not using them, and your problem has nothing to do with Dovecot..

On Mon, 2006-04-24 at 14:57 +0100, Obantec Support wrote:

----- Original Message ----- From: "Timo Sirainen" <tss@iki.fi> To: "Obantec Support" <support@obantec.net> Cc: <dovecot@dovecot.org> Sent: Monday, April 24, 2006 2:00 PM Subject: Re: [Dovecot] LOCK FILE

what form do dovecot .lock files take for mbox files under /var/spool/mail/%u currently i see username.lock with a PID:myservername owned by usersUID:usersGID

Dovecot uses that form, but I think so do many other programs also.

are you saying by having

#mbox_write_locks = dotlock fcntl #mbox_read_locks = fcntl

dovecot is not using locking?

I mean if you have:

mbox_write_locks = fcntl mbox_read_locks = fcntl

Which I think you said a few mails ago that you tried?