> > Possible avenues: allow transport::port and :port, > A domain-less next-hop destination (:port) would break the scheduler, > which schedules deliveries by the next-hop destination. Note that > the scheduler does not know about host:port syntax, nor does it > know which delivery agents support that syntax.
> > or create the 'smtp' equivalent of lmtp_tcp_port. > This would take a very small amount of code, because the functionality > for setting the destination port already exists for LMTP. It would > require changes to the SMTP client loop detection code, which is > disabled for destination ports other than SMTP. Thanks very much for the insight Wietse. If I manage get it working I'll submit a patch. Jason
