Peter Brezny wrote:
>
> Hello,
>
> I'm working on configuring qmail with vpopmail.
>
> I would like to be able to specify the location for mail storage
> specifically for each virtual domain.
>
> Is there a way to do this?
Yes.
[kbo@orbital vpopmail-4.9.7]$ ./vadddomain -v
version: 4.9.7
vaddomain: usage: vaddomain [options] virtual_domain [postmaster
password]
options: -v prints the version
-q quota_in_bytes (sets the quota for postmaster account)
-b (bounces all mail that doesn't match a user, default)
-e email_address (forwards all non matching user to this
address)
-u user (sets the uid/gid based on a user in /etc/passwd)
-d dir (sets the dir to use for this domain)
-i uid (sets the uid to use for this domain)
-g gid (sets the gid to use for this domain)
-a sets the account to use APOP, default is POP
Notice the -d option. (sets the dir to use for this domain)
One thing you'll have to check is the ownership of every
directory in the path. the file system might prevent
vpopmail from writing to the directories.
Another thing I don't like, but it's how it currently works is
-d /home/joe/mail "domain name"
option will actually put the mail in
/home/joe/mail/domains/"domain name"
The -u uid and -g gid and also work ;]
You'll need the new development version. I'll post it
later tomorrow. It has some other internal (major) changes.
I'm tired of hearing about NFS file locks being broken.
So I'm modularizing the functionality into the different
auth modules (file, mysql, sybase, oracle, ldap).
Now the only file based locking ( for mysql at least) will
be for adding or deleting a domain. ;] Much less often then
modifying user informations.
The other thing I'm adding, cause I need it, is changing how
IP alias/domain name mapping is done. I done with DNS lookups.
Now there is a modularized ip-to-domain-name mapping. I've
Written the file and mysql modules (again, it's api/modularized).
Woop
Ken Jones
