On 15 Feb, LuKreme wrote:
| Current recipe:
|
| VERBOSE=ON
| :0c
| * ^Content-type:(.*\<)multipart.*boundary="\/.*[^"]"
| {
| BOUNDARY=$MATCH
| :0 Bfw
| * ^Content-type:(.*\<)text/html
| | sed -e '/Content-Type: text\/html;/,/$BOUNDARY/d'
|
| [...]
|
| so sed,-e '/$BOUNDARY/d'
|
| is failing to match that boundary, but does match the boundary on the
| previous condition:
|
| procmail: Executing " sed -e '/Content-Type: text\/html;/,/$BOUNDARY/d'"
|
| What am I missing?
I haven't tested it, or even looked closely at the recipe, but I'd
guess it's the hard quotes (') around the sed command. The $BOUNDARY
variable will not be expanded. Try soft quotes (") instead in all the
sed commands that use environment variables.
--
Email address in From: header is valid * but only for a couple of days *
This is my reluctant response to spammers' unrelenting address harvesting
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail