Well, I've finally found the cause of my problem. Here is a piece of my
config file (exim 4.69, acts as a relay for internal mail servers):
####################
# My router; blackholes only those recipients who aren't listed in
$acl_m3; doesn't run at verify stage
blackholes:
driver = redirect
condition = ${if ! match{$acl_m3}{$local_part@$domain}}
data = :blackhole:
no_verify
# Default router; runs at verify stage
dnslookup_relay_to_domains:
debug_print = "R: dnslookup_relay_to_domains for $local_part@$domain"
driver = dnslookup
domains = ! +local_domains : +relay_to_domains
transport = remote_smtp
# !!!!!!! The option below causes a problem !!!!!!!
same_domain_copy_routing = yes
no_more
####################
After removing "same_domain_copy_routing" option from "dnslookup..."
router everything is working correctly - "blackholes" router runs for
EVERY recipient (regardless of whether recipients are in the same domain
or not) and regardless of whether condition was not met for some
recipient.
Hmmmm.... Should "same_domain_copy_routing" option (available for ONE
router) affect the functionality of the OTHER routers? Bug or feature? :-)
Regards,
Vitas,From wbh@??? Mon Oct 06 14:13:50 2008
Envelope-to: exim-users@???
Received: from lindfield.ch ([203.194.153.81]:55430 helo=conducive.org)
by tahini.csx.cam.ac.uk with esmtp (Exim 4.69)
(envelope-from <wbh@???>) id 1KmpuH-00046K-PK
for exim-users@???; Mon, 06 Oct 2008 14:13:50 +0100
Received: from cm61-18-24-7.hkcable.com.hk ([61.18.24.7]:64601 helo=pb.local)
by conducive.net with esmtpsa (SSLv3:AES256-SHA:256)
(Exim 4.63 (FreeBSD)) (envelope-from <wbh@???>)
id 1KmpuG-000CaM-1S
for exim-users@???; Mon, 06 Oct 2008 13:13:48 +0000
Message-ID: <48EA0F0B.60400@???>
Date: Mon, 06 Oct 2008 21:13:47 +0800
From: W B Hacker <wbh@???>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1
MIME-Version: 1.0
To: exim users <exim-users@???>
References: <OF8759E8B4.F51DF42C-ONC32574DA.003F6D20-C32574DA.0045B994@???>
In-Reply-To: <OF8759E8B4.F51DF42C-ONC32574DA.003F6D20-C32574DA.0045B994@???>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.7 (-)
X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL=0.184, BAYES_00=-1.5,
DNS_FROM_SECURITYSAGE=1.513, EXIM_DRIVER=-1, EXIM_EXP_VAR=-1,
FORGED_RCVD_HELO=0.135 autolearn=no version=3.1.8
Subject: Re: [exim] Ha: Re: How many times does router run for multiple
recipients?
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject=unsubscribe>
List-Archive: <http://lists.exim.org/lurker/list/exim-users.html>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject=help>
List-Subscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2008 13:13:50 -0000
vitas1@??? wrote:
> Well, I've finally found the cause of my problem. Here is a piece of my
> config file (exim 4.69, acts as a relay for internal mail servers):
>
> ####################
> # My router; blackholes only those recipients who aren't listed in
> $acl_m3; doesn't run at verify stage
> blackholes:
> driver = redirect
> condition = ${if ! match{$acl_m3}{$local_part@$domain}}
> data = :blackhole:
> no_verify
>
> # Default router; runs at verify stage
> dnslookup_relay_to_domains:
> debug_print = "R: dnslookup_relay_to_domains for $local_part@$domain"
> driver = dnslookup
> domains = ! +local_domains : +relay_to_domains
> transport = remote_smtp
> # !!!!!!! The option below causes a problem !!!!!!!
> same_domain_copy_routing = yes
> no_more
> ####################
>
> After removing "same_domain_copy_routing" option from "dnslookup..."
> router everything is working correctly - "blackholes" router runs for
> EVERY recipient (regardless of whether recipients are in the same domain
> or not) and regardless of whether condition was not met for some
> recipient.
>
> Hmmmm.... Should "same_domain_copy_routing" option (available for ONE
> router) affect the functionality of the OTHER routers? Bug or feature? :-)
>
> Regards,
>
> Vitas,
*anything* that satisfies a router condition so as to trigger it
'affects' all *subsequent* routers.
- the message 'falls through' the trapdoor of the satisfied router.
Gone.
Handed-off to a transport to be precise.
Nothing left for any subsequent router to 'see'.
Elvis has left the building. Or at least the hallway where the doors to
routers are. Taken his keys with him, as well.
*anything* that FAILS to satisfy a router condition i.e. does NOT
'trigger' it, affects all subsequent routers in a different way.
- the message is still there, continues the march, worst-case being seen
by ALL routers and satisfying NONE of them. Think handfull of door keys.
NB: Should be obvious that the sequence is quite critical, as first
satisfied means no further tests.
UNLESS the 'unseen' is used.
That has the effect of making a copy of the message before dropping the
original through the trapdoor leading to the transport.
The 'effective copy' continues down the router walk, looking or another
door that will open to (one of) its key(s).
Further 'unseen', if any, repeat the 'clone and continue' effect.
HTH,
Bill
