on 6/5/01 2:04 PM, Joel B. Laing at [EMAIL PROTECTED] wrote:
> The Doctor wrote:
>>
>> On Tue, Jun 05, 2001 at 11:20:07AM -0400, Joel B. Laing wrote:
>>>
>>> The Doctor wrote:
>>>>
>>>> queston:
>>>>
>>>> Using Qpopper 4.0.3 how can one set up qpopper to listen on
>>>> ports 110 (unsecure) and 995 (secure)
>>>>
>>>> I have compiled all the certs and is ready to go, but even all the
>>>> Qualcomm pages cannot seem to answer this.
>>>>
>>>> Does anyone have this set up successfully?
>>>
>>> Yup, works fine, you just need to modify inetd.conf and services. Have
>>> separate config files in etc (apop.conf and popper.conf) for the
>>> different behaviors. You should also look at your firewall rules if
>>> applicable.
>>>
>>> For example,
>>> inetd.conf:
>>>
>>> apop stream tcp nowait root /usr/local/etc/apop apop -f
>>> /etc/apop.conf
>>> pop3 stream tcp nowait root /usr/local/etc/popper
>>> popper -f /etc/popper.conf
>>>
>>> services:
>>>
>>> apop 995/tcp # Apop
>>> pop3 110/tcp # Popper
>>>
>>> Read the INSTALL file for the config options. Sorta depends on exactly
>>> what you are trying to accomplish. You probably want the "non secure"
>>> popper to accept both clear text passwords and apop, and the "secure"
>>> one to only authenticate via apop. Also, if you port forward 110 to 995
>>> at the firewall, you can prevent users from having to reconfigure their
>>> clients.
>>>
>>> Hope this helps,
>>> Joel
>>
>> Why apop on port 995?
> Actually, I use a different port than 995. 995 is what you used in your
> question. I did not realize that that is used by TLS... The same basic
> setup applies, however, unless there is something about TLS I don't
> understand (which is quite likely). You can call the service anything
> you want, the point is using inetd and services to facilitate different
> instances of popper on separate ports, which is in essence what you are
> trying to do.
>
> -Joel
>
GET ME OFF THIS LIST ...
HELP................
HELP.........................
I WANT OFF THE LIST.................
