the following question may sound a little dumb
Nope - lots of people have problems with this.
:0:
^ From(_dot_)*dertagsend(_at_)oscar(_dot_)spiegel(_dot_)ision(_dot_)net
{
:0 c
spiegel-mime
:0
/var/mail/nils
}
First, your condition line doesn't make sense - I presume you didn't cut
and paste it correctly.
That second colon in ':0:' to set a lockfile doesn't make sense in the
context of a recipe when the action is a nesting block[**] (i.e. when
you're using { curly braces }). You want to apply the locks on the
nested recipes like:
:0
* ^From(_dot_)*dertagsend(_at_)oscar(_dot_)spiegel(_dot_)ision(_dot_)net
{
:0 c:
spiegel-mime
:0:
/var/mail/nils
}
I have the feeling that what this message is telling me is not really a
problem, but it would probably still go away when I'd start my recipe with
":0" instead of ":0:".
It is a problem - it's telling you that the locking isn't set up right!
On another recipe, which I included below, I do not get a "locallockfile
warning" like with the first one above.
:0:
^ *TOcvs-all(_at_)freebsd(_dot_)org
Lists/FreeBSD/cvs-all
I presume you have:
* ^TOcvs-all(_at_)freebsd(_dot_)org
But in this case your action is delivery to a mailbox, not a nesting
block, so the local lockfile flag makes sense.
([**] if you use the 'c' flag when the action is a nesting block then
procmail doesn't think that the ':' flag is a problem - but this is a
whole other story!!)
Hope that helps,
Martin
--
Martin McCarthy /</ http://procmail.non-prophet.org
`Procmail Companion' \>\
Addison Wesley /</ PGP key available
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail