Sacha Sardo Infirri kept getting "extraneous locallockfile ignored" warnings.
Philip Guenther had advised:
G: Looking at the procmail source, this warning only
G: occurs if you put a locallockfile on a nested block:
G: :0:
G: * conditions go here
G: {
G: # yadah yadah yadh
G: }
Sacha responded:
I> It appears the the message is being generated by a
I> recipe of a slightly different structure:
I> :0
I> * cond1
I> {
I> :0 c
I> * cond3
I> ! someone(_at_)blah(_dot_)blah
I>
I> :0:
I> Personal/personal.mail
I> }
and asked,
I> Is it ok to put
I>
I> :0
I> Personal/personal.mail
I>
I> in the last recipe of the block?
Philip answered,
G> Unless Personal/personal.mail is a directory, I would not do so.
G> If it's in berkeley mbox format then you should [definitely] leave
G> the colon there.
So that brings up a question: if $MAILDIR/Personal/personal.mail is a
directory, could *that* be the reason for the "extraneous locallockfile
ignored" warnings? After all, local lockfiles are unnecessary on saves
into directories.