At 07:15 2004-05-19 +1000, Marvin Pierce wrote:
The confusion for users trying to understand procmail is its misuse of
some words and the use of when you can or should use a colon.
If you say so. procmail isn't a tutorial on system file locking and
security - there's limits to how much its own man pages should need to
explain things from the ground up - there's other manpages for that.
I'm using maildir formatted mailboxes herein lies the confusion, man
says you don't need lockfile.
What type of file is your ACTION line DELIVERING to?
Wha, wha, wha, it isn't delivering to a MAILDIR? You're delivering via a
pipe to a program???
When running formail via a pipe, you're NOT delivering to a maildir --
you're piping to a program. Here, the need for locking is to protect the
integrity of the file which formail is manipulating, which most assuredly
is not maildir anything. It isn't even a mailbox.
:0 a: for that flag in the same recipe? I don't know the man is not
clear. It says I don't need it and so does Nancy's tutorial.
No. In fact, on that recipe, you wouldn't add locking of any sort because
the ACTION is a braced construct, not delivery to a file, directory, or
even program.
[big snip - no need to include cruft not pertaining to the thrust of the
reply -- that includes prior sigs and list footers]
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail