have you tried putting an email size restrictor on the spamassasin call.
Most spam emails are small, so anything over say 256000 bytes is most
likely not spam and you can let it through untested. This might not be
good for you though if you are also testing for virus attachments.
richard
On Thu, 2003-06-12 at 16:16, Daniel Bendersky wrote:
> --
> [ Picked text/plain from multipart/alternative ]
> Hi,
>
> I want to configure my Exim with spamassassin. I have the exican-acl
> patch so I can use ACL rules to filter the mesages, but the load of the
> server increased to much if I filter all messages.
>
> I used this after the "begin acl":
>
> check_message:
> warn message = X-Spam-Score: $spam_score ($spam_bar)
> spam = nobody:true
>
> warn message = X-Spam-Report: $spam_report
> spam = nobody:true
>
> warn message = X-Spam-Flag: YES
> spam = nobody
> accept
>
> And the load went from 0.5 to 60 so I cannot use this to ALL the
> messages. So I want to configure it only to a group of users that I
> have identified under an LDAP flag.
>
> The question is what is better, to build a router and in that router
> put a system filer that evaluate if the user need to be checked and if
> then, filter the messages, or there is a way to do it directly in the
> ACL ?
>
> Any ways, what you recomend to implement this? I apreciate any
> suggestion/ experience that want to share.
>
> Thanks.
> --
> Saludos....
>
> Daniel Bendersky.
>
> ------------------------------------------------------------------
> Daniel Bendersky Director de Operaciones y Tecnología
> dbenders@??? http://www.netline.cl
> NETLINE Av. Vitacura # 2939 of. 202
> Oficina : +56 2 751 2600 Las Condes, Santiago - CHILE
> Celular : +56 9 998 9122 Fax2mail : +56 2 751 2651
> Voice2mail: +56 2 751 2618
> "Success is a journey, not a destination"
> ------------------------------------------------------------------
> --
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
