At 08:12 PM 7/18/01, Randall Gellens wrote:
>At 3:04 PM -0700 7/18/01, Steven P. Donegan wrote:
>
>> I've done the deeds with qpopper compiles, certificate stuff, etc. Set up
>> inetd.conf so ports 110 and 995 are running qpopper - the first with no ssl
>> configs, the second with ssl set up.
>
>You may want to enable STLS on the pop3 port (110). No reason not to,
>really. That way more modern clients that support STLS will work.
I run Qpopper with one config file on port 110 and one on port 995. The one
on port 110 is set up to use STLS. The one on port 995 is set to force SSL
start. That way I have both capabilities, and can support Outlook and
Eudora. Now if we could only convince Microsoft that they should handle
STLS on SMTP, we'd be in good shape... they presently don't support STLS at
all, it seems, and if you specify you want to use encryption, they assume
the ports start in SSL (works OK for popper as I've configured it, but
isn't workable with SUBMISSION).
To set up the two ports, the key is to build two qpopper.cfg files, one for
each case, and set them up in inetd on the appropriate ports.
-----------------------------------------------------------------
Daniel Senie [EMAIL PROTECTED]
Amaranth Networks Inc. http://www.amaranth.com
