On Tue, 28 Feb 2006, Charlie Brady wrote: > On Tue, 28 Feb 2006, John Peacock wrote: > > Devin Carraway wrote: > >> It's a pretty short adjustment to forkserver; we already can listen on > >> multiple addresses, allowing a port number to be included is easy enough. > > > > Hmmm, I never looked at the forkserver code. I'll take a look at > > implementing this, because I would very much like to eliminate the extra > > stunnel setup... > > stunnel is doing a different job. You can't accept connections on port 465 > and port 25 and treat them equally and expect things to work.
I think you realized it: The one program can certainly treat each connection differently on the basis of which port it comes in on - just direct it to the appropriate code. Since a port 465 (587 even) connection is often considered standard, it would be reasonable to expect an smtpd to handle it. (Hint Hint) :-) If it hasn't been integrated by the time I need or want it, then I'll just have to implement stunnel as well as qpsmtpd :-/ (Although Ask liked my NATting of port 587 (and for now, 465) to port 25, I personally think that capability should be handled within the application, not by something external. Same with the 'stunnel' capability.)