Re: exiscan spamassassin conditions

Alright, but you can't do that for this one as far as I know:
# Reject spam messages with score over 12, using an extra condition.
  deny  message = This message scored $spam_score points. Congratulations!
        spam = $recipients:true
        condition = ${if >{$spam_score_int}{120}{1}{0}}

Say I added a custom field in the database or even just instead of
required_hits add a deny_after so customers can set their own deny level
instead of having the default of 12.

username              preference        value   prefid
-------------------------------------------------------
[email protected]   required_hits     3.9     2
[email protected]   deny_after        9.0     3

Ideas on getting this to work?  I've done database queries but I'm
assuming I'll have to take the 9.0*10 but I can't seem to get anything
to work in the condition..


Also, my spam = $recipients isn't even what it should be as that will
only look at the first recipient correct?  I stuck that in as a quick
solution for the time being.  CC's won't be seen by this will it?

Lance

On 10/29/2004, "Adrian Woizik" <[email protected]> wrote:

>* Lance | 2004-10-28 10:51:28 [-0600]:
>
>>I'm not quite sure I follow on this.  How would exim know when to
>>rewrite the subject if there is no condition telling it when?  If I took
>>the condition out wouldn't it be rewriting the subject for all messages
>>then?
>
>consider the line "spam = user" as a condition which only matches if SA
>says it is spam (reached the required_hits in SA). If you want to always
>add a header, when running SA use "spam = user:true".
>
>see the exiscan spec files for more examples.
>
>regards,
>--
>Adrian Woizik
>
>