John Horne <[EMAIL PROTECTED]> writes: > On Fri, 2002-05-31 at 23:13, Harry Putnam wrote: >> John Horne <[EMAIL PROTECTED]> writes: >> Your observation got me closely checking my home made rules and >> edits. I checked by commenting them all then, uncommenting one by >> one. I found that this rule seems to be the culprit: >> header FW_LOG Subject /\[0030AB066D5C\]/ >> I can't see anything wrong with it, but if I comment it out the error >> stops. >> > Try just removing the '[' and ']' characters. I see nothing obviously > wrong, but if anything is going to cause a problem I guess it would be > the brackets.
Turned out to be the missing `=~' in the above cited header FW_LOG rule >> These two rules: >> >> score Virus_scan_report 1.5 >> header Virus_scan_report Subject =~ /Virus found .* message/i >> >> Should give a message with this subject line: >> Subject: Virus found in the message >> A score of at least 1.5 but messages with that subject go thru and do >> not get any score at all. >> > No score at all, or simply a score less than your required_hits? I could > understand the latter if other tests were causing the overall score to > be marked down. No score at all in some cases. But this also was a result of the poorly formed `header FW_LOG' missing `=~' I think. I'm guessing an error like that throws a monkey wrench into the whole config file containing it. Can someone confirm that is correct? That is, that a rule based on: `header SOME_INDENTIFIER Subject /REGEX/' with no `=~' or `!~' between Subject and /REGEX/ would cause other rules in the config file to give unexpected results. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
