you should install phpMyAdmin. This will allow you to use the interface to edit the values in dir_control table.
FWIW I think QMT had this issue since, at least, ver 1.3... prior to that I don't know. The field is allaways 0 but at some point , after qmailadmin I think, it gets maxed out. 2007/7/16, Dan McAllister <[EMAIL PROTECTED]>:
OK... this is the 3rd time this has happened to me, and the "fix" I've used in the past just isn't feasible this time... I've got a domain on a qmail-toaster (I've tried migrating to qtplus, but the sandbox creation always fails because of the symbolic links and additional mounted filesystems (backup and home are on separate drives)... but that's another story)... The issue is that after running fine for a while, a domain's mysql database gets reasonably well corrupted. At current, if I do a vdominfo on the domain, it shows what I suspect is an error associated with doing signed arithmetic on an unsigned value, or vice-versa. The number of users is being reported as 2147483647 (which is 7FFFFFFF in hex). If I run vuserinfo, all the expected users show just fine, however * something* in qmail-smtp is reporting that there are no users in the domain (all users are bouncing mail as "no mailbox here by that name") -- so I suspect qmail-smtp is using the # of users value and finds it too large. I've had this problem before, but on much smaller domains. Previously, to resolve this problem, I have backed up the old mailboxes, deleted the entire domain (vdeldomain), deleted ALL of the mysql databases (rm -rf /var/lib/mysql/*), re-started mysql (to generate new base databases in /var/lib/mysql), reset the mysql default password, added the vpopmail mysql database, re-added each of the users (plus aliases, forwards, etc.) manually into the vpopmail database, verified correctness, then finally restoring the old mailbox entries. *There has to be a better way! *(With this particular domain, that'll be an all-day project! Over 150 users!) Surely this mysql database entry that has counted the # of users can be fixed somehow WITHOUT starting from scratch! I'm no database guy, but I am a pretty astute Linux (UNIX) admin... so I'm hoping someone out there with the MYSQL knowhow can lead me in the right direction to fix this ASAP! Thanks in advance, Dan Daniel McAllister, President IT4SOHO, LLC 2171 Wrens Way Clearwater, FL 33764 877-IT4SOHO: Toll Free 727-647-7646 In Pinellas 813-464-2093 In Hillsborough 727-507-9435 Fax Only "When did you do your last backup?" Ask me about unattended backup solutions... to protect your business, not just your data!
-- AM agmsoft(at)gmail.com
