procmail
[Top] [All Lists]

Re: Dup check, no dumping of message?

1999-10-31 16:31:08
++ 31/10/99 14:43 -0600 - David W. Tamkin:
To alter the text of the current message and go on processing more recipes,
you use the `f' flag (filter).  The `c' flag (copy) is for delivering a copy
of the message to that recipe's action and going on reading more recipes to
deliver the original.

Ok... that's basic and i would have corrected later on. But the thing i
was looking for if this filtering actually would do what i would like it
to do. It does.

LOCKFILE=msgid.lock
:0hwf
* ? formail -D 8192 msgid.cache
| formail -A "X-Duplicate: yeah baby"
LOCKFILE # release the regional lock

Here's an equivalent:

:0Whc:msgid.lock
| formail -D 8192 msgid.cache
 :0afwh # in case of success (i.e., if it is a duplicate)
 | formail -A "X-Duplicate: like, fer sherr"

If there are any differences in results or operation between those two,
I hope one of the experts will let us know.

I think i prefer the first, looks a bit clearer. Maybe that's not the
most important thing to base the decission on, but as i have a
completely commented procmailrc i prefer recipes that are as clear as
possible.

BTW, I'm greatly in favor of setting PATH and calling executables by their
basenames over setting variables for every executable's absolute path and
invoking them all by their variables.

Why is that?

        -Rejo.

-- 
= Rejo Zenger  [Sister Ray Crisiscentrum]               
rejo(_at_)sisterray(_dot_)xs4all(_dot_)nl
= http://mediaport.org/~sister                                  PGP: see headers
--------------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>