Hello Andrea, On Wednesday, January 14, 2004 at 7:08:39 PM you wrote (at least in part):
>> If you don't find any error logs about vchkpw failed to write >> data to 'open-smtp' insert a 'strace' or similar behind >> ssl-listener ... > Could you send me an example? > Something like 'strace openssl s_client -connect 127.0.0.1:995'? In your 'run' script give this a try: [...] /usr/local/bin/sslserver -v -R -H -l 0 0 995 \ strace -f -s 4096 -o /tmp/ssl-pop3.log \ /var/qmail/bin/qmail-popup \ [...] Don't let this run when "real" users try to log in, the password will be in '/tmp/ssl-pop3.log'. Use this only with test accounts, if you intend to publish the log (or relevant excerpts from it) in this list. If you don't intend to do this we will probably not be able to help. >> Maybe a permission problem? Is ssl-listener or vchkpw not >> started as 'root' or 'vpopmail' (or whatever your vpopmail >> user is named)??? > My /home/vpopmail/etc: [...] > After a connection via pop3-ssl, I've this /home/vpopmail/etc: [...] Looks like vchkpw is run as root, therefore a pure problem with permissions is more or less unlikely. -- Best regards Peter Palmreuther No problem is so formidable that you can't just walk away from it.
