Rejo Zenger <subs(_at_)sisterray(_dot_)xs4all(_dot_)nl> writes:
Oke, i changed to that second version. It works perfect, but i would
like to see one thing change.
This is what i have in the logs when no dups are found:
procmail: Locking "msgid.lock"
procmail: Executing "formail,-D,8192,/home/rejo/.log/msgid.cache"
procmail: Program failure (1) of "formail"
procmail: Assigning "LASTFOLDER=formail -D 8192 /home/rejo/.log/msgid.cache"
procmail: Unlocking "msgid.lock"
When a dup if found:
procmail: Locking "msgid.lock"
procmail: [1637] Tue Nov 2 09:02:17 1999
procmail: Executing "formail,-D,8192,/home/rejo/.log/msgid.cache"
procmail: [1637] Tue Nov 2 09:02:17 1999
procmail: Assigning "LASTFOLDER=formail -D 8192 /home/rejo/.log/msgid.cache"
procmail: Unlocking "msgid.lock"
procmail: Assigning "nl"
procmail: Assigning "nl="
procmail: Assigning "notice=X-Note: Message-ID seen before recently."
Can i get rid of this 'Program failure' in the first case? I know it is
completely correct, but i'm sure i will get confused because of it one
day or another... like when grepping logs on 'failure' or 'error'. Can't
there be a more descriptive or rephrased line there?
This was previously discussed on the procmail development list and it
was agreed that in the next version of procmail, if a program fails
that is executed as a condition or as the action of a recipe with the
'W' flag, then procmail will instead log the message:
procmail: Non-zero exitcode (nnn) from "x"
Note that even in current versions of procmail, the "Program failure"
message for programs invoked under the conditions listed above is only
logged if VERBOSE is on, so if you don't want to see those messages,
don't turn VERBOSE on. Program actions that fail on recipes with the
'w' flag will still be logged even if VERBOSE is off.
Philip Guenther