Re: How spam ACLs work

Hello - To do what you request:

1. The spamd check is done on the first request of the scanning and not
repeated.

2. I would also add a warn - is was not scanned becaues it was too big ie:

 #  ADD 80K spamd limit for spamd scoring

  warn  message = X-FINE-Spam-Score: Your message was NOT scanned for Spam Score
 Messages of this size are unlikely to be SPAM.
        condition = ${if >{$message_size}{80k}{1}{0}}

3. To each other 'spam' check add the condition check ie:

  # Reject spam messages with score over 8, using an extra condition.

  deny  message = Rejected due to Spam detection by Spamassassin. This message s
cored $spam_score points.  Refer to http://finearts.uvic.ca/sim/email/ for infor
mation.
        condition = ${if <{$message_size}{80k}{1}{0}}
        spam = nobody:true/defer_ok
        condition = ${if >{$spam_score_int}{80}{1}{0}}


Dave,

Quoting Jason Leach <[email protected]>:

> hi,
>
> With respect to the exiscan smapassassin ACL, I have a few options:
>
> warn (add the score)
> warn (add scanned header)
> warn (score over 5 add ***SPAM*** to subject)
> deny (score > 12)
>
> It works great.  But I need to limit the size of spam scanned mail to
> 80K.  Would I add an accept rule before all my 'warn' rules?  Or has
> spam scanning already been done at thsi point? Does the scan take
> place in my first 'warn' rule or does a scan take place for each one?
>
> Can I use multiple 'condition = ' clauses?
>
> Thanks,
> Jason.
>
>
>


-- 
David Broome   Senior_Programmer-Analyst.FineArts.UVic.CA  /BSc
250.721-6307   [email protected]                    FIA 221