Mark wrote,
| I am having troubles getting procmail and formail to drop in a header line.
| It looks like the problem is a semi-colon in the header. The current
| recipe looks like
|
| :0 wfh
| * ? is8bit < tmp.request > /dev/null
| | formail -b -I"Mime-Version: 1.0" \
| -I "Content-Type: text/plain; charset=iso-8859-1" \
| -I "Content-Transfer-Encoding: 8bit"
| It returns
|
| Content-Type: text/plain
| Content-Transfer-Encoding: 8bit
| If I escape the semi-colon with a \, I get
|
| Content-Type: text/plain\; charset=iso-8859-1
Something sounds goofy, as if your shell can't handle a semicolon inside
quotes as an ordinary character. What is $SHELL set to?
| If I save the SHELLMETAS and run it directly from procmail, it chokes on
| the arguments in the Condition line.
Well, that's a clue in itself; what happens if you try this?
oldmetae=$SHELLMETAS
SHELLMETAS="<" # appears in the condition but not in the action
:0 wfh
* ? is8bit < tmp.request > /dev/null
| formail -b -I"Mime-Version: 1.0" \
-I "Content-Type: text/plain; charset=iso-8859-1" \
-I "Content-Transfer-Encoding: 8bit"
SHELLMETAS=$oldmetae
I must admit to being unsure why you're using formail's -b option if you're
filtering only the head.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail