On Sun, 6 Dec 1998, Lutz Pressler wrote:
> What I would like to see is for Exim to remember the connected local
> address for remotely queued messages within the spool header file and
> then have a special value for the SMTP transports' interface option
> which tells it to use that (or even the result of a lookup operation)
> as the source address.
I don't think I quite understand. Exim already stores
sender_host_address in the spool header file for messages that have come
from a remote host. Is this what you are wanting, or is there something
else I have missed? Are you just wanting to be able to say
interface = $sender_host_address
in the smtp transport?
> In principle this should not be difficult to do, I think. The more
> complicated part will be the code that reuses SMTP connections to the
> same destination which has to differentiate by source address now, too.
That would be hard, because you can't discover the sender_host_address
without reading the message's header file, and Exim does not do that at
the right time. I don't think this could be done at all easily without
major nasty hacks to the code.... thinks ... well, what might work is to
key the records in the waiting database by interface as well as by
remote IP address. If you did that, it might be reasonably
straightforward, now I think about it.
> What does it do at the moment if multiple SMTP transports with different
> "interface" options are used? Have not looked yet.
Each SMTP transport has its own "waiting" database.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
