At 16:25 2007-01-07 +0800, DR. Lee - NS3 wrote:
[snippety-do]
procmail: Executing "echo ${TO}| sed -e "s/\"[^\"]*\"//" -e
"s/\(<\([^>]*\)>\)/\2/g" -e "s/^[ ,]*//" | tr -s " ,"
"\n""
???? how came this variable get data like this and it happened very
often ????
procmail: Assigning "MY_TO=This account is currently not available."
[snip]
Looks like a message from a bogus shell. Funny, given you were running
command pipelines before, I'd have expected your shell was functional. Of
course, you never posted logs, and you weren't doing assignments...
try:
SHELL=/bin/sh
at the top of the procmailrc.
[snip]
So, I set up a liltte file to test the sed command and assgiment of
MY_TO:
[snip]
The result is not the same; if the pattern is in the varialbe MY_TO, it
match the first string and the string followed is errored by "No such
file or directory". Writing to file and then grep seems ok.
You're running from a shell when you run your shell script, so presumably
you have a valid shell at that point.
I take it you'd previously piped messages at the recipe using a sandbox,
and it seemed to work, but when you put it into your live config, you
started getting errors. Any chance your email is processed via an NFS
mount? The host actually handling mail doesn't have a legitimate login
shell for you to use.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail