Jakob Hirsch wrote:
> Quoting W B Hacker:
>
>> Use of '$interface' and 'helo_data' should allow you to force what Exim uses to
>> match what you have already published in the DNS.
>
> It was pointed out a few times on this list that you cannot user
> $interface there, because the transport does not know, which address
> will be used for the connection (except if you explicitely set it, but
> then you know it already).
Sorry - the '$' was superflous.
SB: 'interface'
- a parameter for the smtp transport.
>
> If I'm not mistaken, $interface_address and $interface_port are only set
> for incoming connections. This should probably be said in the spec. Philip?
>
You are not mistaken, and those *are* so described in the spec, but not germane
to the issue at hand.
Routers need to make a selection of which fixed transport to use, *or* hand a
single transport data from a lookup, or the key it needs to DO a lookup.
How the routers select, on what basis, and why so, is a separate item.
...but 'fixed' transports chosen might look something like these:
=========
remote_smtp_2_ctyme:
driver = smtp
interface = 69.50.231.2
helo_data = "2.ctyme.com"
remote_smtp_5_ctyme:
driver = smtp
interface = 69.50.231.5
helo_data = "5.ctyme.com"
==========
