"@lbutlr" <kremels(_at_)kreme(_dot_)com> writes:
I have the following in my sms include.
MSGTEXT=`/usr/local/bin/formail -I ""| /usr/local/bin/lynx --dump
--dont_wrap_pre -stdin`
And then
MSGTEXT=`echo $MSGTEXT | sed '/:$/d' |sed '/^>/d'`
SMSTEXT=`echo $MSGTEXT | sed -e 's/^ //' |sed -e 's/[-=_]//g'| tr '\n' ' '
| cut -c1-140`
This SOMETIMES results int eh following errors:
procmail: Excessive output quenched from "/usr/local/bin/formail -I ""|
/usr/local/bin/lynx --dump --dont_wrap_pre -stdin"
procmail: Excessive output quenched from "echo $MSGTEXT | sed '/:$/d' |sed
'/^>/d'"
You would think this happens with excessively long messages, but it
doesn't. Some of the messages are quite short, though they will be
messages with multiple parts (usually a txt and an HTML portion).
I suppose it depends on what "excessive output" means... The HTML from
most HTML message is "excessively long" in my opinion!
But in any case, you want to use:
MSGTEXT=`echo "$MSGTEXT" | sed '/:$/d' |sed '/^>/d'`
SMSTEXT=`echo "$MSGTEXT" | sed -e 's/^ //' |sed -e 's/[-=_]//g'| tr '\n' '
' | cut -c1-140`
without the quotes, the shell will mutilate the text of your messages.
In particular, it will change newlines into spaces. Perhaps "excessive
output" really means "excessively long output lines".
Dale
____________________________________________________________
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