Thats what have done:

I wrote this configure scripts:

----> tssl_popper.conf:

# QPopper-configfile
# for SSL Connections at port 110
#
set tracefile = /var/log/popper.log
set tls-support = stls
set config-file = /etc/QPopper/common_popper.conf
<-----------------

-----> alt_popper.conf:

# QPopper-configfile
# fuer SSL Verbindungen auf Port 995 (klassisch)
#
set tracefile = /var/log/alt_popper.log
set tls-support = alternate-port
set config-file = /etc/QPopper/common_popper.conf
<-----------------


-----> commom_popper.conf

# set debug = true

# some options
set uw-kluge = true
set statistics = true
set log-login = true
set timing = true
set timeout = 600

# the cert and the server key
set tls-server-cert-file = <somewhere>
set tls-private-key-file = <somewhere>
<-------------------

Compiled popper with
./configure --enable-log-login --enable-standalone --with-openssl=.../openssl-0.9.6b 
--with-pam --enable-timing --disable-update-abort   
(Ok, it's a little bit ultra.)


The daemons started via:

/usr/sbin/popper -f /etc/QPopper/tssl_popper.conf 
/usr/sbin/popper 212.201.18.80:995 -f /etc/QPopper/alt_popper.conf


I can have alternate connections on port 995 and normal SSL connections on port 110.
If you set the clear_text_password option right, it should be possible to
only have SSL only connections (on both ports, or on one port, do what you like)
I don't test it yet.

But the above settings working for me (on a heavy stress system, perfectly).


- oliver

Reply via email to