Phil Pennock wrote:
> On 2008-01-23 at 01:19 -0800, Justin Tan wrote:
>> I would like to configure exim to use Mailscanner whitelist.
>> I have tried
>> exim -be ${lookup{\NFrom\:\t
>> $hostname\N}lsearch{/etc/MailScanner/rules/spam.whitelist.rules}}$value
>> It does not gives any hope.
>>
>> /etc/MailScanner/rules/spam.whitelist.rules look like this:
>> #######################################################
>> FromOrTo: *@domainname.com yes
>> From: *@fromdomainname.com and To: *@todomainname.com yes
>> #######################################################
>>
>> Can anyone help me regarding this
>
> I can't think of a way to do this natively with Exim's config language.
> Can't you use a script to build lookup rules in a format more suitable
> for Exim?
>
> Otherwise, I suspect that you need to look into building Exim with the
> optional embedded Perl interpreter and using that.
>
> -Phil
>
Exporting part of the mailscanner file may be easier, as you don't
necessarily have to do it in 'real time' to get decent gain.
If you can get it into the format where each line is a *domain.tld or
*prefix.domain.tld:
*example.com
*prefix1.example.com
*prefix2.prefix1.example.com
Then you don't necessarily need to hold the 'FromOrTo', 'From', 'To' as
separate records.
You can use separate *files*.
ELSE separate parameters in lookups run by different acl's on the SAME
file (which is what I do here).
Ex:
condition = or !condition = one of:
${lookup{$sender_host_name}wildlsearch{/filename}{yes}{no}}
${lookup{$sender_helo_name}wildlsearch{/filename}{yes}{no}}
${lookup{$sender_host_address}wildlsearch{/filename}{yes}{no}}
${lookup {$sender_address}wildlsearch{/filename}{yes}{no}}
Not optimal, but works for me...
Bill
