cat(_at_)zip(_dot_)com(_dot_)au followed up,
| Hmmm. This is the part of the manpage that worries me:
|
| $ Evaluate the remainder of this condition according to
| sh(1) substitution rules inside double quotes, skip
| leading whitespace, then reparse it.
Sean has already answered that: it says procmail acts according to sh's
rules, not that it uses sh. Consider these: procmail uses sh's rules even
if $SHELL is csh or a csh derivative, which would behave differently, and if
$SHELL is a superset of sh such as bash or zsh or ksh, procmail's variable
substitution for "$" modification still doesn't handle any of the additional
syntaxes that those shells know.
I'd said,
2. procmail does any backticked command substitution where the command
string has no characters from $SHELLMETAS; and
and cat responded,
| This seems to be for pipes:
It also applies to "?" exit code conditions: if there are no characters from
$SHELLMETAS in the command, procmail runs it itself.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail