Re: [Exim] Processing Spam for Other Email Servers

Top Page
Delete this message
Reply to this message
Author: John W. Baxter
Date:  
To: Exim-Users (E-mail)
Subject: Re: [Exim] Processing Spam for Other Email Servers
On 5/3/2004 10:09, "Tor Slettnes" <tor@???> wrote:

>
> On May 3, 2004, at 08:09, Marc Perkel wrote:
>
>> I have a server running exim that is set up to filter spam and viruses
>> for other email domains and then pass the mail on to their existing
>> email server. Right now the way it works is that they point their MX
>> records to me and I have to add their domain to a file telling the
>> system where to forward the processed mail once it is done.
>>
>> Router looks like this:
>>
>> process_and_forward:
>> driver = manualroute
>> domains = +preprocess_domains
>> condition = ${if match{$h_X-Spam:}{HIGH}{no}{yes}}
>> transport = remote_smtp
>> route_list = *
>> ${lookup{$domain}lsearch{/etc/exim/preprocess}{$value}{}}
>> no_more
>>
>> And it works great - but I want to further automate it.
>>
>> What I want to do is if my server is the MX server for the domain, I
>> want to forward it to smtp.$domain but only if smtp.$domain is defined.
>> Still trying to figure out all the details of how to set this up but
>> I'm
>> trying to figure out a way that people can self configure email
>> forwarding through my system.
>
>
> You could use "domains = @mx_any", then:
>     condition = ${if and {!match {$h_X-Spam:}{HIGH}}\
>                          {eq ${lookup dnsdb{a=smtp.$domain}{yes}{no}}
> {yes}}\
>                      {yes}{no}}
>     route_list = * smtp.$domain

>
>
> Let me know when you have this in place, I'll switch my MX to point to
> you. :-)
>

Also, it seems to me that we had a thread recently about mx_any suffering
badly from domains which announce their MX as 127.0.0.1 as a means of no
longer getting mail.

mx_secondary probably solves that, leaving only the "more users than I
wanted" problem.

--John