Re: [exim] relative 'expense' of Exiscan/SpamAssassin vs. lo…

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Brian Candler
CC: exim-users
Subject: Re: [exim] relative 'expense' of Exiscan/SpamAssassin vs. local_scan for simple header/body triggers?
On Sun, 18 Sep 2005, Brian Candler wrote:

> Aside: the idea that it would be nice to be able invoke the exim *filter
> language* during ACLs has occurred to me more than once. Perhaps a "filter =
> <filename>" or "filter = <string>" condition would do this. Applications:


Permissions issues would make this fail frequently, and therefore cause
administrative hassles.

> - invoking a user's filter during DATA would allow messages to be rejected
> rather than accepted and subsequently blackholed (yes, I know there's a
> problem for messages with multiple recipients)


The problem is kind of show-stopping...

> - invoking another user-written filter at RCPT stage would allow users to
> customise policy for message rejection. For example, Exim could previously
> set $acl_m0 to the number of RBL lists which a message has triggered,


I suspect very few users would be knowledgeable enough to do this kind
of thing.

-- 
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book