[ archivemail-Bugs-855269 ] need an option to skip procmail_lock

[SourceForge.net <no...@so...>]

Bugs item #855269, was opened at 2003-12-06 12:08
Message generated for change (Settings changed) made by nikosch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=456910&aid=855269&group_id=49630

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Karl Chen (quarl)
Assigned to: Nikolaus Schulz (nikosch)
Summary: need an option to skip procmail_lock

Initial Comment:
To operate on mboxes in e.g. $MAIL=/var/mail/$USER, 
you can't use procmail locks (/var/mail/$USER.lock)
since you don't have write permission to that
directory.  Since procmail doesn't write there either,
this should be allowed via a command-line option (or
even automatically detect if directory is not writeable
by user)

----------------------------------------------------------------------

>Comment By: Nikolaus Schulz (nikosch)
Date: 2010-08-09 12:49

Message:
archivemail 0.8.0 skips dotlocking if it hasn't sufficient privileges to
create the dotlock file.

----------------------------------------------------------------------

Comment By: Nikolaus Schulz (nikosch)
Date: 2007-11-09 04:08

Message:
Logged In: YES 
user_id=1594781
Originator: NO

Okay, I see this is a problem. 

As far as I know procmail *does* dotlocking in /var/mail. I am not an
overall Unix wizard, but on my Debian boxes, /var/mail is writeable for
group mail, and there exist several utilities for dotlocking, all of which
are setgid mail.  

The mailbox module in python 2.5 does indeed just skip dotlocking, if the
program has no write permissions. Of course that's not really ideal. :-)
archivemail could search for known dotlocking utilities and try to acquire
a dotlock with their help... I have to think about it. 


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=456910&aid=855269&group_id=49630