why not write your own rules as extension? I have some 500+ rules to stay (ahead|close) to spammers...
ie.: rawbody RAWBODY_PORN_OBFUS_01 /(\$ex|pr0n|p0rn|t(\||\!|1|í|ì|î)t|fvck|a\$\$|cl(\||\!|1|í|ì|î)t|c0ck|pen(\| |\!|1|í|ì|î)(s|$)|b0y|d(\||\!|1|í|ì|î)ck|(\||\!|1|í|ì|î)nche?s?|erect(\||\!| 1|í|ì|î)on|(guarante(é|è|ê)d|guarant(é|è|ê)ed))/i score RAWBODY_PORN_OBFUS_01 8.3 describe RAWBODY_PORN_OBFUS_01 Porn indication (and obfuscates it) rawbody RAWBODY_PORN_OBFUS_02 /\b([A-Z]+[$|!il0][A-Z]|[A-Z]+[$|!il0][A-Z]+)\b/ describe RAWBODY_PORN_OBFUS_02 Porn indication (and obfuscates it) Version 2 score RAWBODY_PORN_OBFUS_02 4.4 cheerio Btw.. I saw earlier on this list someone suggesting "degappyfying" text before running through tests.. Couldn't a "de3133+ing" be done before running some tests to avoid all those p0rn, rem0ve, e-mai1? (Well, bayes could of course pick those up after I run them through sa-learn, but there are many ways to spell a word "wr0ng") ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
