sa-compile and backlashes

fro|\|". Not sure what it's doing. Any solution other than commenting out the offending rules? -- Gus

Re: sa-compile and backlashes

Gus wrote: Sorry if this has come up at all, but I have a few rules that sa-compile chokes on. Wondering if there's a way around it... Here's an example. Original rule: /(?:fr(?:o|0|\(\))(?:n|\|\\\|)[EMAIL PROTECTED])/i Sa-compile seems to interpret every branch of this, so we e

Re: sa-compile and backlashes

2c up because that creates an incorrect amount of "'s. I even tried escaping it has hex "\x52" (or whatever the right number was--don't have my ascii table handy anymore :). -- Gus

Re: [OT] Seeing increase in smtp concurrency ?

less. When it hit 1500, we moved a few of our rbls to the connect phase, which brought it down to about 150 exim procs. Yeesh... -- Gus

Re: Compiling Rules

/spamassassin/3.002003" for default rules dir [17010] dbg: config: using "/etc/mail/spamassassin" for site rules dir You can also pick a custom body rule that you made and grep that: sa-compile -D --list 2>&1 | grep TEST And get results like: orig TEST_0001 /test01010101/i r test01010101:TEST_0001 -- Gus

Display DCC results in headers

dunno if anybody'll find it useful, but since I did it I figured I might as well share it just in case. I'm sure now that I've gone to the trouble somebody's going to point me to some "dcc_add_header 1" config variable that I overlooked. ;^) -- Gus

Re: Compiling Rules

/spamassassin/3.002003" for default rules dir [17010] dbg: config: using "/etc/mail/spamassassin" for site rules dir You can also pick a custom body rule that you made and grep that: sa-compile -D --list 2>&1 | grep TEST And get results like: orig TEST_0001 /test01010101/i r test01010101:TEST_0001 -- Gus

Display DCC results in headers

dunno if anybody'll find it useful, but since I did it I figured I might as well share it just in case. I'm sure now that I've gone to the trouble somebody's going to point me to some "dcc_add_header 1" config variable that I overlooked. ;^) -- Gus

Re: Compiling Rules

Sorry for the dupes. Had a wrong setting in mutt and thought these two didn't get sent properly. :-/ (my solution to this problem being to send a third message... Hmmm...) -- Gus

Re: bayes_seen = 256GB

0mb. :) To make it expire, either set bayes_auto_expire to 1 and let it expire tokens automatically, or run sa-learn --force-expire and sa-learn --sync. -- Gus

Re: Bit OT but it's about SPAM

had we given them the chance. -- Gus

Re: help with training bayesian filter

us header still says "autolearn=no". Do I need to > enable autolearning in some other way? Do you have bayes_auto_learn set? That's what turns it on/off. -- Gus

Re: Received from rule?

mail3.example.com <http://mail3.example.com> Something like header HappyRuleName Received =~ /mail\d\.example\.com/i or header HappyRuleName Received =~ /^from mail\d+\.example\.com/i ? -- Gus