Shortly after my computer died, Roland Hill asked in response to one of
the last posts I typed on my old machine,
I assume the above example assumes delivery to a mbox style of dir?
It could; if the folder is a qmail-style maildir, then it needs no local
lockfile. Actually, if it's any kind of directory, no local lockfile is
necessary or advisable, but some people have insisted (for reasons I
caould not follow) that classic procmail directories and MH-style
directories potentially need serialized writes, although problems from
not locking the delivery are far less likely than they are with mboxes.
I am
using the Maildir format (not that I expect you to guess that), so I have
assumed that I don't need a lockfile. Is that correct? Is it always
correct not to have a lockfile on delivery recipes when used with the
Maildir format?
Considering the confusion we already have over maildir and MAILDIR, when
a question uses the orthography "Maildir" away from the beginning of the
sentence is that I am reluctant to answer it. If you'll change
"Maildir" to "maildir" at both occurrences, then yes, delivery to a
maildir requires no local lockfile, and asking procmail to secure one
(which it will do, the default name being $LOCKEXT [which is usually
".lock"] one directory up in the maildir itself rather than in the new/
subdirectory where it's writing the message) is a waste.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail