Hi
> fgp> There is an explanation for virtualdomains/multiple users with signed system
> fgp> user/uid on www.qmail.org.
>
> I'm not sure I find this or not. I didn't find something literally that,
> but I found many "virtual" things there. Part of the problem, I think, is
> that there isn't a precise meaning for "virtual".
Well.. you are right - but "virtualdomain" ist quite precise, if you stay in
the qmail context ;-)
> fgp> It is bases on the users/assign file (in /var/qmail/users/assign). This
> fgp> files tells qmail where mail to a certain user shall be delivered too (thus
> fgp> overiding /etc/passwd). This together with the virtualdomains files gives
> fgp> you excellent support for a _lot_ of domains and a _lot_ of users. Note that
> fgp> (as far as I remember) the user/assign file is _compiled_ into some sort of
> fgp> binary file, so it should be fast also with a lot of entries.
>
> If it uses /var/qmail/users/assign then it's not what I want, and not what I
> call virtual. To me, one of the attributes of virtual is that there is no
> table of mapping between a user e-mail address and where to deliver, but
> instead, the determination of where to deliver is a functional relation to
> the e-mail address.
It�s virtual, the same as you have "virtual" http-hosts...
But I guess I know what you want - from the address [EMAIL PROTECTED], you
want the mail to be stored in "/somepath/domain.com/user" - not a
"static" mapping, "calculated" from the address? Then you could think about
patching/rewriting qmail-local - altough maybe you should hink about writing
you own smtp-server/mda for that purpose.
> I want the very minimum of administrative work to manage it. This will
> require such things as automatically deriving the user authentication data
> from the customer account database. I expect to write something that will
> rebuild certain files (password CDB, rcpthosts, virtualdomains) from the
> data obtained from the database.
jes - create /users/assign from the database.. ;-))
> I don't want a .qmail file for each user (except for local host users). If
> by leaving it out I can deliver to each users's maildir, that' what I want.
>
> At the same time there may be a catch. The default delivery for the local
> host (e.g. listed in locals, for users in /etc/passwd, with distinct uids),
> is not maildir, but "./Mailbox". I need to be able to leave local users as
> all "./Mailbox" by default (unless overridden in a .qmail file for each user
> individually), yet have maildirs used for all the virtualdomains users without
> creating zillions of .qmail files.
you could make .qmail files for local users, overiding the Maildir default
to Mailbox - or just take one machine for all those thousands of users and
"virtual"domains, and another one for the shell accounts.
> We'll be doing the web interface for administration as an integral part of
> the whole internet service administration, working through a central database
> that records every service, not just e-mail. E-mail configuration will then
> be derived from that database much like web configuration, DNS configuration,
> and so forth. I will be able to add a new customer, specify domains, and
> let them add their own users and subdomains, and it will automatically set
> up their e-mail, radius for dialup, routing for dedicated DSL, web service,
> and whatever else (the exact system hasn't been chosen, yet).
Wow.. Zero Administration ISP - sounds quite cool.
Greetings, Florian Pflug
