"David W. Tamkin" <dattier(_at_)ripco(_dot_)com> writes:
Dallman has a point: not everyone, despite strong advice, uses a non-csh
shell for procmailrc actions with shell metacharacters. Maybe the implicit
local lockfile name code could deal with >>! by stripping the exclamation
point and adding $LOCKEXT. Any chance that that would break existing recipes
that append to files whose names begin with exclamation points? Would it be
necessary to check first whether $SHELL's antepenultimate character is `c'?
I've considered for a while changing procmail to always set SHELL to
/bin/sh and put the user's shell in USER_SHELL or some such variable.
That would seem to solve the underlying problem though it would break
anyone depending on procmail's use of their login shell.
Anyway, this is really a topic for the procmail-dev mailing list, so
I've cross-posted and directed followups there.
procmail mailing list