Timothy Luoma <luomat(_at_)peak(_dot_)org> writes:
...
:0fhw
...
| $FORMAIL -I"X-SpamChecker: PASSED" -I"X-SpamNote: ByPassed"
...
but it still wasn't working.... well, dumbo finally figured out that he
had FORMAIL= in his .procmailrc at home, but NOT in the .procmailrc at the
account where this was failing 8^}
This is just one of the reasons that I recommend *not* using variable
to store command paths or names. Generally you should just set PATH
correctly at the top of your .procmailrc (assuming that the default
wasn't correct), and then call commands with plain names. I've heard
only one moderately good reason to use explicit variables, and that
could have been solved more cleanly in my opinion, with a directory
containing a few symlinks.
I therefore request of those who maintain procmailrc archives, that
they eliminate the use of variables to store command names or paths in
the procmailrcs that they distribute, and instead include a comment or
suggestion regarding the setting (or just adding to) the PATH
variable.
Philip Guenther