"John D. Hardin" <jhardin(_at_)wolfenet(_dot_)com> writes:
On Fri, 16 Feb 2001, Philip Guenther wrote:
"John D. Hardin" <jhardin(_at_)wolfenet(_dot_)com> writes:
On Thu, 15 Feb 2001, Jonathan Baker-Bates wrote:
procmail: Excessive output quenched from "formail"
Using a variable capture recipe instead of a variable assignment
with backquotes in the value may be the Right Way to solve the
problem, but we would have to know what Jonathan is trying to do
to be sure.
There are only two places the sanitizer uses formail:
...
Assuming that the error message he included was literal, then no shell
was involved in the command that was executed: if one was then the error
message would have included the entire command being invoked. Since both
uses of formail by the sanitizer require a shell to be invoked, those
cannot be the source of the error message. The error must be coming from
a formail invocation in a variable assignment outside of the sanitizer.
He should turn on verbose logging and track it down from there.
Philip Guenther
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail