Well, the invocation for a specific machine is quite useful, thanks.
I eventually bit the bullet and moved the affected users to the main
machine. To get the queued messages delivered, I added the 'othermachine'
to the local_domains, and tweaked the local DNS to map othermachine to
exim_machine for a couple of minutes.
At 18:33 03/03/00 +0900, Jim Tittsler wrote:
>On Thu, Mar 02, 2000 at 03:10:15PM +0000, Jim Cheetham wrote:
> > However, today all I'm getting for these users are lookup failures :-
> > $ /usr/exim/bin/exim -bt user@othermachine
> > user@othermachine cannot be resolved at this time:
> > host lookup did not complete
>
>It looks like a DNS problem rather than an Exim or networking problem.
>One way you might insulate yourself a bit from this... especially if you
>know othermachine.domain.name is a single host with a constant IP address
>would be to add a router that syphons off those addresses and uses the
>IP address directly.
>
>other:
> driver = domainlist
> domains = "othermachine.domain.name"
> transport = remote_smtp
> routelist = "* 10.10.1.2 byname"
>
>
>--
>Jim Tittsler, Tokyo
>Python Starship http://starship.python.net/crew/jwt/
>
>
>
>--
>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
>details at http://www.exim.org/ ##
--
Jim Cheetham, Reading Room E: J.Cheetham@???
T: +44 20 7734 9499 F: +44 20 7692 5560 W:
http://www.rroom.co.uk
