I formulated a query string and did an strace on qmailadmin from the shell. Inside the output, I found some stuff like this:
open("/usr/lib/mysql/libmysqlclient.so.10", O_RDONLY) = 3
connect(5, {sa_family=AF_UNIX, path="/var/lib/mysql/mysql.sock"}, 110) = 0
open("/usr/share/mysql/charsets/Index", O_RDONLY|O_LARGEFILE) = 6
etc
I didn't find any references to vchkpasswd in the strace...and I'm not using MySQL for auth.
I remembered that a few months ago, Inter7 was in doing some work for me -- they migrated my users over from vpasswd to a MySQL database. We had some problems and had to roll the changes back. I guess that we forgot to roll back qmailadmin, which is why it was still checking against the MySQL DB. The reason that it was able to authenticate at all was because the old users were already in the DB (I think).
In any case, I was able to rebuild qmailadmin and everything is working properly.
Cheers!
-Ethan P
ethan-lists writes:
Hello,
I'm currently running qmailadmin 1.0.6 with vpopmail 5.3.20 and have been having some strange issues over the past few months.
After I added my first 100 users (I use vadduser from the commandline to add users), another directory was created, "0/" the next hundred users -- and presumably, the following hundred users will reside in the "1/" directory.
My problem is this:
All of the users in the "0/" directory are not recgonized by qmailadmin. I'm unable to see those users in the Postmaster's list, and they're not able to log into qmailadmin.
Everything else seems to work properly. Those users are able to authenticate via vchkpw for sqwebmail, courier-imap, and qmail's esmtp auth.
I tried screwing around and creating accounts with qmailadmin and they don't work -- they create a *file* (not a directory) in the domain root and don't seem to do anything with vpasswd.
The vpasswd file seems to put everything in the right place (hence the otherwise working auth).
Anyone have any experience with this? Clearly, I'm doing something wrong here.
