Well, the reason I wanted expanded port strings was so that I could do
on the fly mappings from ports on VM's stack to arbitrary host/port
combos.
However, consider the following scenario--local ports I map are in the
range 50000-50049--I get a mapping of vm:50002 for a remote host and
port that has a transient error.
Now, when I retry that host, Exim is going to retry vm:50002--but 50002
is no longer hooked up to anything. What I want to do is forget that
mapping and just run the transport again, so I get a new host (still vm)
and a new port (let's say it's 50000) this time.
I *think* that setting retry_data_expire to something ridiculously
short, like 1s, will fix this for me. Is that a correct reading of the
spec? So the next time that message gets looked at, we say, "oh, our
cached data has expired, let's ask again," at which point I get the same
host (because it's fixed in $hosts, and hosts_override is set) and a new
port (because generated with a ${run {...}} expansion)?
Adam
