ram wrote:
>>>
>>>

>> Really? It's that bad to add a single, very simple, body regex? Have you
>> looked at how many body regexes the stock SA configuration runs? Have
>> you looked at how many are hundreds of times more complex, just by
>> themselves?
>>
>>
>> For example 20_drugs.cf contains:
>>
>> body __DRUGS_ERECTILE1
>> /(?:\b|\s)[_\W]{0,3}(?:\\\/|V)[_\W]{0,3}[ij1!|l\xEC\xED\xEE\xEF][_\W]{0,3}[a40\xE0-\xE6@][_\W]{0,3}[xyz]?[gj][_\W]{0,3}r[_\W]{0,3}[a40\xE0-\xE6@][_\W]{0,3}x?[_\W]{0,3}(?:\b|\s)/i
>>
>>
>>
>> And question, are you really trying to do this as a whitelist, or are
>> you trying to compensate for the score of one of the standard rules? If
>> you're trying to compensate for a standard rule, you can use it, rather
>> than your own... That way you're not adding any extra regexes, other
>> than the__TO_CC_PHARMA_COMPANY, which is unavoidable to do what you want.
>>
>>

>
>
> Yes but I would want to give an interface to the customer to manage that
> himself. And he cant be expected to know DRUGS_ERECTILE. But he surely
> knows his mails come with viagra or with easy-home-loans
>
> With very little training the admin can himself whitelist words and
> compensate for FP's himself
>
>
>> For example, you could do:
>>
>> meta ALLOW_MEDS (__TO_CC_PHARMA_COMPANY && DRUGS_ERECTILE)
>>
>> The meta rule itself is processor-wise quite cheap.
>>

>
>
> Cheap ok , but until when. How many on such domain specific rules will
> my shared servers support. I dont think this can scale.
>

It will scale better than your suggestion of trying to inhibit rule
loading at runtime.
> Ok so IF-THEN-ELSE rules are not available in SA. Probably that was well
> thought of too. But I think that would be a good feature to have ,
> especially for creating domain specific rules if not have any other
> application
>

Why? It doesn't scale well because it would force re-parsing rules at
runtime. Urgh!

> Thanks
> Ram
>
>
>
>
>
>
>