[EMAIL PROTECTED] wrote:
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.
This code is already committed to branches/0.3x (as I suggested in my
other message). If you run qpsmtpd-forkserver, you can request
listening on multiple ports, include 465 (SMTP over SSL). If you enable
plugins/tls, it will hook connect and automatically start up an SSL
connection for port 465.
I'd like to improve the code, though, so you can request multiple ports
to listen to, while still using the default 0.0.0.0 (all interfaces).
John
