Zlatko

On Sat, 2008-02-16 at 15:55 +0200, Zlatko Mesaros wrote:
> Debug run will follow, and here are the routers:

OK, great - please consider subscribing to the mailing list so that your
posts don't get held for moderation.

My hunch was right:

> amavis:
>         driver = manualroute
>         condition = "${if or {{eq {$interface_port}{10025}} \
>                          {eq {$received_protocol}{spam-scanned}} \
>                          {eq {$sender_address}{}} \
>                          }{0}{1}}"
>         transport = amavis
>         route_list = "* localhost byname"
>         self = send

There's no condition or domain check on your Amavis router which
restricts the spam scanning to, well, anything.

If you compare some of your other routers you'll see a "domains = " line
- this restricts that router to local domains or your virtual domains.

You probably want to add
domains = +local_domains : dsearch;/etc/mail/virtual

to your amavis router.

If you look at your debug run, you'll see that the amavis router
accepted the "random" address you fed in:

> 16:26:54  7963 routed by amavis router
> 16:26:54  7963   envelope to: [EMAIL PROTECTED]
> 16:26:54  7963   transport: amavis
> 16:26:54  7963   host localhost.localdomain [127.0.0.1]
> 16:26:54  7963 ----------- end verify ------------
> 16:26:54  7963 require: condition test succeeded
> 16:26:54  7963 processing "accept"
> 16:26:54  7963 accept: condition test succeeded
> 16:26:54  7963 SMTP>> 250 Accepted

It's also worth noting that you should probably drop the amavis setup
anyway, and have Exim call spamassassin and/or your AV application
directly. That way you'll never accept-n-bounce, but reject at SMTP
time.

Graeme


-- 
## List details at http://lists.exim.org/mailman/listinfo/exim-users 
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to