alan premselaar said: > my question is, why isn't it being processed by spamassassin? if i have an > error in my regex, it complains and i see it in my maillog ... but it > doesn't seem to match
SpamAssassin decodes the headers, that's probably it. Try running "spamassassin -D -Lt < tstmessage", and see what gets reported in the debug output as the decoded subject line, then identify the bit and block on that. Is that definitely what it looks like in "raw" ISO-2022-JP? It seems very base64-ish to my eyes... --j. ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
