I think, that short of modifying the source for ipop3d, you could accomplish this task my using "stunnel" on the server to listen to the desired port for SSL connections and "forward" these to the pop3s port locally. This will ensure that you can have an SSL-only POP connection on an alternate port and will solve the ipop3d port issue. See "stunnel.org".
-Erik Kangas
Mark Crispin wrote:
On Fri, 9 Jul 2004, Ian Hunter wrote:
Does ipop3d check it's name use SSL if it's pop3s and no SSL otherwise?
Correct. ipop3d starts in SSL only when on the pop3s port.
Servers can not use command line arguments, since server argv is used by various accounting packages. Something like "/ssl /tls" in a command line argument wouldn't exist on UNIX anyway (on UNIX, switches start with "-").
You seem to be confused about TLS. TLS is started by a client command, and not by the selection of port. Thus for TLS, it can be on any port since the connection is supposed to start in plaintext.
-- Mark --
http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
--
Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated [EMAIL PROTECTED] --- http://luxsci.com
