ok, i feel like a bit of a dumb ass, my problem was not the same as the problem in the auth mailing list. see, i had been calling the patched qmail-smtpd as follows... qmail-smtpd /home/vpopmail/bin/vchkpw /usr/bin/true well, all this does is have an open relay use you used ANY auth since it thinks the domain is "/home/vpopmail/bin/vchkpw" and the password checker is /usr/bin/true... and of course we already know what true is going to say about every username password it's fed LOL... second, went i did call with with a domain as argument... qmail-smtpd test.com /home/vpopmail/bin/vchkpw /usr/bin/true i had just reinstalled everything ( I have a few scitpts and freebsd packages of qmail etc etc that reinstall in a few minutes ) i forgot to add the test account, so that acocunted for the missing username messages... right after my laptop committed suicide kamikaze style... well, after a quick look over , I realized my dumbness... the right way to call it with vpopmail, is , as you FAQ clearly states.. qmail-smtpd somedomain.com /home/vpopmail/bin/vchkpw /usr/bin/true the reason why i chose to call it without the domain. well, i had seen it on the mailing list. meaning, anyone that is calling it as qmail-smtpd /home/vpopmail/bin/vchkpw /usr/bin/true has got themselves an open relay. as long they input any sort of user/pass conbination. also, having it be called with a domain doesnot limit the athentication of vpopmail, youc an call qmail-smtpd with xyz.com and authenticate with blah.com. hope this helps someone, and thanks kris for a great patch :) Krzysztof Dabrowski writes: > At 23:44 2001-04-25 +0000, you wrote: >> Anyone ever encountered this... using the latest version found here >> http://members.elysium.pl/brush/qmail-smtpd-auth/index.html >> and vpopmail 4.9.10.... > > Ask on the apropriate mailing list (and check archives). > this is a common problem (=misunderstanding of qmail's configuration). > > Kris >
