On 1 May, Lars Hecking wrote:
|
| > # Prepare and send notification
| > # Be sure to customize for your sendmail path
| > | (formail -r \
| > -i "Subject: Returned e-mail: Password or privileges required" \
| > -A "X-Loop: wash(_at_)everest\(_dot_)wananchi\(_dot_)com" ; \
| > echo "************************************************" ; \
| > echo "* This response message is computer-generated.*" ; \
| > echo "************************************************" ; \
| > echo ; \
| > echo "Email password required!" ; \
| > echo "Please include (${PASSWD_}) anywhere on your subject line." ; \
| > echo "Then kindly resend your e-mail to
wash(_at_)wananchi(_dot_)com") ; \
| ^^^
| Swap ) and ; .
|
| > | $SENDMAIL -t
|
| > Syntax error: end of file unexpected (expecting ")")
| > procmail: Non-zero exitcode (2) from " (/usr/local/bin/formail -r \
| > -i "Subject: Returned e-mail: Password or privileges required" \
| > -A "X-Loop: wash(_at_)everest\(_dot_)wananchi\(_dot_)com" ; \
|
I think the trailing semi-colon after the last command is required
inside a group command {}, not inside of a sub-shell (), and I don't
think the trailing semi-colon after the closing paren hurts. But that
assertion is shell based (bash version > 2.0), not procmail based. I
don't know if that's true for sh, or for that matter for whatever shell
Odhiambo Washington (the original author) has set.
But beyond that, I think the log and the copied/pasted recipe (if done
faithfully) are telling a different story.
This line above:
echo ; \
has space(s) after the line continuation (\). [disclaimer] I haven't
checked the rest of the code for errors that might appear after this one
is fixed, because this isn't the kind of recipe I have experience with.
--
/"\
Don Hammond \ / ASCII Ribbon Campaign
Raleigh, NC US X Against HTML Mail,
/ \ and News Too
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail