At 7:51 AM -0400 4/12/02, Mark Wendt wrote: >Any chance we might see in a future release an option to set port >110 as a TLS/SSL only? Currently that option is only available for >the alternate port, 995. We have a requirement to use encrypted >communications only, and we're currently forcing the clients to use >the alternate port. Be nice if we could set port 110 with that >option, and shut down clear text on that port.
Actually, Qpopper doesn't care what port it runs on. The choice of how to support TLS (STLS or alternate-port) is independent of the port number. Some people get confused by this, and try to run on port 995 simply by setting TLS support to alternate-port, without also having Qpopper listen on port 995. Probably the easiest way to ensure encrypted communications only is to set the clear-text-password option to tls. If you don't add APOP support, that forces everyone to use TLS. You can do this independently of which port or how TLS is supported. So you can have Qpopper available on 110 and 995, offering STLS on 110 and alternate-port-tls on 995.
