Florian G. Pflug wrote:
> > 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 ;-)
How about "virtualusers".
What I am looking at doing will include fuzzy matching of existing users
from a database, and optionally users don't need to exist to be delivered.
> > 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...
There's virtual by IP, virtual by Host, and I've twisted both concepts
around using some CGI code, too.
> 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.
That's the point I want to start from. Then from there employ more ideas
to change it even further. It looks like maildir is so simple I can just
do the delivery right in my own code. I won't have to parse any headers.
And presumebly, what qmail-local pipes to my program is exactly what goes
in the file, so it should be trivial.
> jes - create /users/assign from the database.. ;-))
There will be a many-to-one relationship in the address to mailbox mapping.
So this is probably not scalable.
> > 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.
The shell accounts won't go through my delivery program. But if my program
does the actual maildir create/write/link/delete steps, then it won't matter
what the default is, which can stay Mailbox ... everything going through my
program will be maildir anyway. I just need to make sure I'm not going to
run into something unexpected.
> > 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.
Yeah ... put myself out of a job.
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
