* Philip Hazel (ph10@???) [990419 06:12]:
> I think we have to distinguish "LMTP over TCP/IP" and "LMTP over
> file-descriptor". The former could no doubt be done by a flag in the
> smtp transport. However, given the existence of the latter, I think I
> would prefer to have an entirely separate lmtp transport which handles
> both cases via some suitable options, e.g. you set either
>
> lmtp_command = xxxx
>
> in order to run a pipe, or you set
>
> lmtp_hosts = list of hosts to try
That would address the issues that I brought up, but it also means that a
lot of code would be copied from both the pipe and SMTP transports into this
new transport. Granted, I can't see SMTP changing that much in the future,
but it does mean that code changes would have to be made in two places.
> I guess port= would be needed too. Maybe only a single host is needed.
> That would simplify the code quite a lot.
"port =" would be needed, but strangely the RFC doesn't say which port
should be the default. The only mention of a port is that it shouldn't run
on port 25.
--
j.
James FitzGibbon (JF647) james@???
EHLO Solutions Voice/Fax +1 416 410-0100
--
*** Exim information can be found at
http://www.exim.org/ ***
