On Wed, 15 Sep 2004, V. T. Mueller, Continum wrote:
> Can fallback_hosts be combined with a different interface option
> in the same transport?
No.
> Any ideas?
I first wrote:
------------------------------------------------------------------
Don't use fallback_hosts. Instead, add a new router that picks up the
delayed messages and routes them to a different transport. For example:
fallback_router:
driver = accept
... other conditions ...
condition = ${if >{$message_age}{300}{yes}{no}}
transport = fallback_transport
Maybe there is a better condition than testing the message age. In a
system filter, there is a first_delivery condition, but I see that I
haven't implemented an equivalent variable for use in a router. I've
noted this oversight. In the meantime, you could add a header in a
system filter and trigger the router on that (and remove it).
------------------------------------------------------------------
Then I remembered that the interface option is expanded. So you can do
something like this:
fallback_hosts = 1.2.3.4
interface = ${if eq {$host_address}{1.2.3.4}{10.0.0.1}{10.0.0.2}}
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
