https://bugs.exim.org/show_bug.cgi?id=2026
Bug ID: 2026
Summary: expand protocol option on the smtp transport
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: medium
Component: Transports
Assignee: nigel@???
Reporter: km@???
CC: exim-dev@???
Currently protocol option on the smtp transport is not expanded. There are
cases when it's desirable to set protocol based on the value of $host_port.
Summary from discussions on #exim:
21:14 < km_> ah, the protocol option on the smtp transport is not expanded
21:14 < km_> *facepalm*
21:15 < km_> was going to set it to smtp or smtps depending on value of
$host_port
21:24 < hs12> km_: but expansion would be useful there, I'd say
21:25 < km_> yes, I was very surprised that this was a fixed string
21:27 < hs12> technical reason?
21:28 < jgh_> and why not make the port depend on the protocol?
21:28 < km_> I have a transport to do AUTH on outgoing smtp
21:29 < km_> and manualroute router, that sets route_data to host::port
21:29 < km_> host is used to lookup username/password
21:29 < km_> and port might vary between 465, 565 or 587
21:30 < km_> 565 is like 465, but will strip received fields
21:30 < km_> so I thought I'd change protocol depending on port
21:32 < km_> so 1) there's no 1:1 match between protocol and port (in that
order) and 2) port is
set by router anyway
21:33 < jgh_> expansion sound possible; there might be some dependency ordering
issues though.
It'd need a careful look while writing the code
21:38 < km_> I'll be glad if it is added...
21:39 < km_> I also see it being useful where users would not know the
difference between smtp and
smtps, and just provide a port that is given to them
21:39 < jgh_> best to raise a bug so the request doesn't get lost
--
You are receiving this mail because:
You are on the CC list for the bug.
