On Tue, Sep 11, 2001 at 09:32:49PM -0400, Debian User wrote:
> Hello colleagues,
>
> Before I ask you gentlemen my question, let me first say that I HAVE
> READ the qpopper manual, searched these archives and searched on my
> favourite search engines for the answer to my question. My results were
> not helpful.
>
> I am trying to enable qpopper to listen on both ports 110 for apop auth
> and 995 for ssl/tls. I have read the manual and tried to initiate the
> daemons using the three config files, but that didnt work. IT will ONLY
> listen on port 110 and either do apop OR ssl. It will not do both. I am
> not using tcpwrappers (inetd).
This makes it a little more complicated. You're sure you don't want to
do it from xinetd or inetd?
The reason is very practical: that's the way most people run it, so if
you want specific advice with real examples, those are the kind you are
most likely to get.
> My server is operating in standalone
> mode, so I am asking you fine people that subscribe to this list for
> help. How do I tell the server to listen to both ports.
You need to run two different instances of the server in standalone,
with totally different configurations, loaded from the command line via
"-f /path/to/configfile". Start one instance of the server configured
via its config file to listen on port 110 and use apop; start a
different one to listen on port 995 for SSL. BTW, you normally
wouldn't want to do TLS on a different port number than 110, because if
the client's configured for the non-standard port you would expect it
to also be configured for SSL; so you might as well set the port 995
one to use SSL exclusively.
Since I don't run it standalone, this info is all based on a purely
theoretical understanding of how it should work.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
