On Tue, 2 Jul 2002, Oliver Egginger wrote:
> Ultimately, a minor problem, anyhow:
> we switchted from Exim 3 to 4.
> In Exim3 we use the "bydns_mx" option in our "smart_host" configuration.
> This option don't exists in Exim4.
I decided that the manualroute router really should be cleaner, and
implement "route this domain to those hosts".
What you were doing was "route this domain as if it were that domain",
and it seemed to me to be cleaner to keep this as a separate function.
However, I never actually implemented that functionality!
> But our smart host only exists as a MX record.
Then it isn't, strictly speaking, a "smart host". I guess it's a "smart
domain".
> Current this MX record mask two mailhubs.
> In our new Exim4 configuration I use the following route list (which acts as a makeshift):
> route_list = * mailhub1.our_mailprovider.de:mailhub2.our_mailprovider.de bydns
> But I would like to have something like this
> route_list = * smarthost.our_mailprovider.de bydns_mx
> How can I handle this in Exim4 ?
Not easily at present. I was asked this question last week. As a result
of that question, there is now an item on the Wish List.
> I like the MX record solution, because if our provider chance something
> on his host configuration we don't have to pay attention to it.
Many (most?) other smarthost providers use multiple A records instead.
We do it that way. I suppose using an MX does give the option of
different preferences, but in some sense it isn't "right".
> I think I need a route list, therefore I have to use a manual router.
> Could you please give me a hint ?
I think you'll have to wait until I get to that Wish List item. What I
had originally planned was a router called "masquerade", which would
implement "route this domain as if it were that domain". Whether or not
I'll actually do it that way I don't at present know.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
