On Mon, 25 Feb 2002, j2 wrote:
> THis: Not sure how to read it tho, i see what fauils. .but not why.
Exim seems to be OK.
> routing dans@???
It skips routers or declines until
> --------> virtuals router <--------
> virtuals router generated dans@???
Which it obtained by looking up in the file. So it goes on to route
that.
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Considering dans@???
> active address dans@???
> local_part=dans domain=lists.mupp.net
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> routing dans@???
> --------> virtuals_part2 router <--------
It starts at the virtuals_part2 router because of the setting of
redirect_router.
> local_part=dans domain=lists.mupp.net
> checking "condition"
> search_open: lsearch "/etc/exim/routing/routes"
> cached open
> search_find: file="/etc/exim/routing/routes"
> key="dans@???" partial=-1
> LRU list:
> 8/etc/exim/routing/routes
> 8/etc/aliases
> End
> internal_search_find: file="/etc/exim/routing/routes"
> type=lsearch key="dans@???"
> file lookup required for dans@???
> in /etc/exim/routing/routes
> lookup failed
> virtuals_part2 router skipped: condition failure
There is no key in your file for dans@???, so the router
fails.
(Contrast this with j2@???, which generages "j2@???", so in
this case the lookup succeeds.)
The automatic conversion of your configuration hasn't been clever enough
to get this one right.
The best plan would be to figure out exactly what you want to happen,
and then re-organize the routers by hand to achieve it.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
