Qmailadmin is a web-interface interface for managing a Vpopmail-enabled qmail system. You can delegate control over specific domains to end-users, so that they may manage creation of accounts, changing of passwords, etc, within limitations set down by the system administrator.
Keep in mind when troubleshooting Qmailadmin, or vQadmin, or any other program that works on top of vpopmail, that sometimes these errors are actually a result of a problem with the vpopmail configuration, or it's backend authentication systems, rather than the interface using vpopmail.
Error. Domain example.com was not found in the assign file
This error occurs for a number of reasons. Generally it falls into two categories. Resource limitations, and permissions problems. This error is actually generated by the vpopmail library, and not by Qmailadmin, which can make determining the cause of this error for the end-user slightly more difficult.
First, be sure SELinux is not enabled. Since Qmailadmin requires SetUID properties to execute, SELinux may quietly deny this to Qmailadmin at execution time. A quick test for this, is to run the command
# setenforce 0
If that fixes your problem, edit /etc/selinux/config and modify the SELINUX configuration to read
If SELinux was enabled, and this did not fix the problem, reboot your mail server and see if that disables SELinux. If you're still having problems, there may yet be other permissions problems. Check the following permissions:
# ls -dl /var /var/qmail /var/qmail/users /var/qmail/users/cdb drwxr-xr-x 24 root root 4096 Jul 27 2004 /var drwxr-xr-x 17 root qmail 4096 Feb 15 13:04 /var/qmail drwxr-xr-x 2 root qmail 4096 Feb 15 11:11 /var/qmail/users -rw-r--r-- 1 root root 2355 Feb 15 11:11 /var/qmail/users/cdb
The groups may differ, but the permissions should match. Make sure your domain exists in the cdb file.
# strings /var/qmail/users/cdb | grep example !example.com-example.com /home/vpopmail/domains/example.com
If it doesn't, rebuild the cdb file, and try Qmailadmin again.
If all else fails, it may be a resource issue. If you're using MySQL as a backend, be sure Qmailadmin is able to contact the MySQL server. Be sure you have enough available resources for Qmailadmin to open the cdb file.
Gentoo users may need to emerge the newest 1.2.9 ebuild, as per http://forums.gentoo.org/viewtopic-t-467890