the stupid solution is to chmod 644 the vpopmail.mysql file, although it works.
Amazingly stupid. Anyone with access to that machine can learn your MySQL password for the vpopmail database and use it to read passwords, make changes or just delete everything.
Very bad idea.
How about making it group readable, and having all of your domains set to use vpopmail's gid (but the user accounts would NOT use vpopmail's gid). chmod 640 vpopmail.mysql, chmod 770 the domain directory.
another solution would be to change the uid/gid for that domain in qmail's assign file to 89/89 (vpopmail's uid/gid) and then chown vpopmail.vchkpw the "domains" dir in 510/510's home dir AND the home dir itself (or chmod 744 510/510's home dir). i don't like this solution either as i want to keep 510/510's home dir owned by that user AND have 700 permission for privacy.
What's wrong with keeping all of the domains in ~vpopmail/domains? Why do your users need access to their domain directory if they have qmailadmin to manage it?
so the only other solution which i could think of was to set that domain's uid/gid as 0/0 in qmail's assign file. now, what kind of security risks could this setup pose? i'm brand new to qmail, so i'm not sure (just installed it a few days ago).
Not a good idea. Any file qmailadmin creates will be owned by root and other utilities managing the domain won't be able to change it.
-- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
