RE: How spam ACLs work

"Andrew Whyte" <[email protected]> Wed, 3 Nov 2004 10:48:07 +1000
Newsgroups gmane.mail.exim.exiscan.user
Message-ID <741CFAAFD0EA2A40B9FD0B39FC0D4F80046D9114@ROKEMAIL.staff.ad.cqu.edu.au>
I have the same setup, and I opted for the accept above the spam rules
with a condition on size.  It works a treat.

something like :

        accept  condition = ${if >{$message_size}{100k}{1}{0}}

followed by your other spam rules...

Cheers, Andrew
 

> -----Original Message-----
> From: Jason Leach [mailto:[email protected]] 
> Sent: Wednesday, 3 November 2004 10:42 AM
> To: [email protected]
> Subject: [exiscanusers] How spam ACLs work
> 
> 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.
> 
> 
> 
>