Folks,
I really appreciate any feedback on this issue (see below), i.e. if it's
valid for exim 4.x, too.
The thread can be viewed at
http://marc.theaimsgroup.com/?l=amavis-user&m=103703996324340&w=2
Thanks a lot!
best regards,
Rainer Link
-------- Original Message --------
Subject: Re: [AMaViS-user] exim, amavis and receiver_verify (was:
[amavisd] Suggestion to improve README.exim) (fwd)
Date: Mon, 11 Nov 2002 22:20:59 +0100
From: Rainer Link <link@???>
Organization:
http://www.openantivirus.org/
To: amavis-user@???
CC: dominik+usenet@???
References: <Pine.LNX.4.33.0211111924410.29078-100000@???>
<87wunjq5br.fsf@???>
Hilko Bengen wrote:
> Rainer Link <link@???> writes:
>
>
>>Could any exim guru please comment on that one? Thanks!
>
>
> Dominik is right.
>
> Since in the standard setup, the amavis router/transport is the first
> set of rules that is evaluated for any message, it does make sense to
> put the verify* statements here.
Ok, so the following would be correct?
amavis_director:
condition = "${if eq {$received_protocol}{scanned-ok} {0}{1}}"
driver = smartuser
transport = amavis
# verify must be set to false, to avoid troubles with receiver and/or
# sender verify
verify = false
amavis_router:
condition = "${if eq {$received_protocol}{scanned-ok} {0}{1}}"
driver = domainlist
route_list = "*"
transport = amavis
# verify must be set to false, to avoid troubles with receiver and/or
# sender verify
verify = false
Or should I probably elaborate a bit more on this topic? Is it valid for
Exim 4.0, too?
Comments, suggestions and so on _very_ welcome. I consider updateing the
FAQ wrt this topic, too.
Thnaks.
best regards,
Rainer Link
