S.Toms had asked -- maybe there's been a reply but I don't remember --
regarding some advice from Philip,
| pg> I see two other bugs in the above: $sendmail should be capitalized and
|
| Does it have to be capitalized though? I agree with capitalizing the
| variables to distinguish them, but if he sets the variable with lower
| case, won't that work?
If the person wants to use procmail's compiled-in value for $SENDMAIL or the
same program that a "!" action will use, yes, it has to be capitalized.
Nothing will stop you from using "sendmail" as the name of another variable
in your rcfile, but I think it's a bad idea as it can be too easy to confuse
the two.
| pg> there should be a space before the backslash that continues the first
| pg> line of the action. As it was originally written without indentation,
|
| Does that also include lines that end commands with ;\ ? I have various
| filters that have ;\ immediately following the command line, where as I
| have just a space \ when its a formail argument.
The semicolon is in $SHELLMETAS, so its presence will invoke a shell, and
the shell will interpret it. Shells with which I'm familiar don't require
spaces around a semicolon, so if the shell sees
command1;command2
that won't bother it. Thus the semicolon is an exception. But a space
between the semicolon and the backslash wouldn't hurt, and it's a better
habit always to use the space than never.
| Why was the closing parenthesis placed on the same line as the sendmail
| command?
Philip's personal preference.