Jim asked:
> Using the recipe below, I get a MATCH when encountering
> multipart/alternative, but not for text/html. (I haven't experienced
> any text/enriched yet on this test run). The recipe succeeds for both
> cases, but text/html leaves MATCH empty.
[stripping the recipe down to just the condition]
> * ^Content-Type: \/multipart/alternative|text/(html|enriched)
which equals,
* (^Content-Type: \/multipart/alternative)|(text/(html|enriched))
The way you have it written, the part of the expression that matches
when "text/html" or "text/enriched" occurs before (or without)
"<newline>Content-Type: multipart/alternative" doesn't include an
extraction operator in it, so MATCH is left alone. If it wasn't set
earlier, it's still unset. Note also that you can get a match on
"text/html" or "text/enriched" with "<newline>Content-Type:<space>"
nowhere to be seen.
Try
* ^Content-Type: \/(multipart/alternative|text/(html|enriched))
> Maybe I've made a typo I simply can't see.
That's where my money is.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail