dattier(_at_)wwa(_dot_)com (David W. Tamkin) writes:
Philip Guenther wrote,
| You can already do all of these right now: (1) is the normal situation,
| (3) and (4) are easy: just do the filtering before or after you do the
| matching. The only tricky one, (2), can be done using the trick
| described by David Tamkin:
Wait, Philip, you mean my suggestion WORKS? That has to be the best thing
about procmail I found by sheer dumb luck since the "{ }" no-op.
Stephen strived hard (strove?) to make things work as intuitively as
possible. Here again he succeeded.
| :0 c:
| {
You'll need to name the lockfile there. But wouldn't a `W' or `w' flag do
the job instead of (and more efficiently than) a lockfile [unless some actual
file needs serialized writes]?
Correct. ":0 cW" would probably be the normal set of flags for this.
Without either a 'w' or 'W' flag, or a lockfile, the exitcode of the
child procmail would not be saved as the parent would have no reason to
wait for it.
Philip Guenther