dovecot - May 2013 - change inbox dotlock name

Hi,

Is there a configuration element that would allow me to change the 
dot-lock name for the user's /var/mail inbox when it is locked?  dovecot 
(correctly) acquires <username>.lock, but I'm having a problem with 
procmail where some obscure code path is preventing procmail's 
acquisition of a lock when it's that default name in /var/mail.

The issue is not permissions (using a world-writeable and sticky-bit 
config for /var/mail).

I'll dig into the procmail code if needed, but if dovecot could use a 
different filename for such locks, then that would solve my issue.  
procmail has such an option, and I only need to do this for inboxes.

Thanks,
Chris

-- 
Chris Saldanha
Parliant Corporation

Le 8 mai 2013 ? 14:42, Chris Saldanha a ?crit :
> Hi,
> 
> Is there a configuration element that would allow me to change the dot-lock
name for the user's /var/mail inbox when it is locked?
Hello Chris,

This seems to be fully hard-coded.

> dovecot (correctly) acquires <username>.lock, but I'm having a
problem with procmail where some obscure code path is preventing procmail's
acquisition of a lock when it's that default name in /var/mail.
But I fear I don't understand your problem description.
Could you elaborate?

Axel

Axel Luttgens <AxelLuttgens at swing.be> wrote:
 > But I fear I don't understand your problem description.
 > Could you elaborate?

Hi Axel,

The issue is that the procmail port on FreeBSD doesn't acquire a dotlock 
when it's the default lock file (/var/mail/username.lock).  It prints 
that it's bypassing the dotlock and just does a lockf() lock after.  
Looking in the code for procmail, it seems that it's being too clever 
with a bunch of checks and so it doesn't try to get the lock -- it's 
decided it doesn't want to before doing it.

The permissions and runtime environment permit the lock, and the same 
lock is acquired correctly by dovecot when writing to the inbox.  I'm 
doing dotlock and then lockf() locking in all the mail software.

procmail's checks only seem to apply to the default lock file for the 
inbox.  If I specify an alternate name in the .procmailrc for the 
$ORGMAIL delivery of the message, then it will acquire any other lock I 
ask, including an alternate name in the /var/mail directory.

I'll dig into the procmail sources as needed to resolve it, but I had 
hoped that I could get dovecot to lock with a different filename, 
because that would resolve the issue with minimal hackery...

Cheers,
Chris

-- 
Chris Saldanha
Parliant Corporation