[See http://mla.libertine.org/tmda-users/2003-09/msg00362.html for reference if you don't read -users]
Tim Legant <[EMAIL PROTECTED]> writes on tmda-users: > Anyhow, I'll try to get a look at the RFC2047 stuff, if Jason > doesn't get to it first, to solve the particular problem you're > having. It's not a bug on our part, it's simply how we chose to implement the content matching features. We pass the headers into FilterParser as a raw, undecoded string. It wouldn't be that difficult to decode the headers before re.search()'ing if the user wanted that behavior. I'm not sure this should be the deefault behavior though. Perhaps a '-decode' option to the body* and headers* rules or something? _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
