Hi folks, As I said, I've tested the qmail-pop3d daemon over ssl with ucspi-ssl (http://www.superscript.com/ucspi-ssl/intro.html). My runscript was: #!/bin/sh CAFILE="/usr/local/ssl/certs/pop3s.cert" CERTFILE="/usr/local/ssl/certs/pop3s.cert" KEYFILE="/usr/local/ssl/certs/pop3s.key" DHFILE="/usr/local/ssl/certs/dh1024.pem" export CAFILE CERTFILE KEYFILE DHFILE exec /usr/local/bin/softlimit -m 3800000 \ /usr/local/bin/sslserver -v -R -H -l 0 0 995 /var/qmail/bin/qmail-popup \ nesys.it /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 2>&1
The vchkpw was compiled with --enable-roaming-users. Well, there's a problem with roaming: the auth is fine, but my open-smtp is blank, and I've some .tmp files in /home/vpopmail/etc, like open-smtp.tmp.<num>. With the normal qmail-pop3d the vchkpw with roaming works correctly, without any problem. Then, question: have you ever been testing the vchkpw auth and roaming option with an ssl connection? I've tested courier-imap's pop3s too, with vchkpw+roaming or vchkpw+relay-ctrl. Courier 2.2.1 doens't work with roaming, but works correctly with vchkpw auth. Courier 2.2.2, in my opinion, has problems with vchkpw auth (where I put my PASS, the ssl session falls). Courier 2.2.1 with vchkpw and relay-ctrl has a security bug (the roaming is enabled for users with wrong pass too). Well, that's cool :) probably there's a strange problem between vchkpw/roaming/ssl connection? I need your feedbacks! Thanks for all Regards Andrea
