On Tue, Nov 09, 1999 at 06:06:03PM -0600, Phil Howard wrote:
> Patrick Berry wrote:
>
> > On 11/9/99 at 3:52 PM, [EMAIL PROTECTED] (Phil Howard) had the thought:
> >
> > > Please don't suggest lots of userids and/or lots of .qmail files. I'm
> > > dead set on making this easy to administer, so those are not options.
> > > That's why I'm running things through a program that figures it out.
> >
> > I could be way off base here, but it sounds like your dead set on
> > reinventing the wheel. If you have to have a directory for the userid to
> > hold the Maildir, what is the problem with having a .qmail file to tell
> > qmail to deliver to that Maildir?
>
> There will be hundreds of virtual domains and hundreds of userids in each.
> No, make that thousands. Maybe more. What's more, the user names will
> be created on the fly, so creating .qmail files in advance for every user
> name just isn't possible.
>
> I don't want to add the extra I/O overhead of creating a .qmail file for
> each user. I'm trying to make this lean and mean. What I want to do is
> divert the .qmail lookup for these virtuals (the ones in virtualdomains
> naming this one single base user that handles this whole mess) so that
> for each user@domain to be delivered there is _not_ a .qmail file there.
>
> If I could code the master .qmail file like:
>
> # note the single quotes here:
> echo './Virtuals/${HOST}/${USER}/' > .qmail
>
> and qmail-local would apply environment substitution, that would do the job.
> But that doesn't work. So I'm trying:
>
> echo '|./bin/delivery-to' > .qmail
>
> where the program in bin/delivery-to examines the environment variables
> and determines the directory to deliver to (all are owned by the one user
> that all this is running under). The next step is to deliver the mail
> there (which I'm wanting to avoid re-inventing, since something in qmail
> can obviously do it).
>
> There would be a corresponding logic for vchkpw authentication and finding
> the directory under the pop3 server, plus a web based access facility to
> be developed, too (I'll be doing this in PHP).
Hi
There is an explanation for virtualdomains/multiple users with signed system
user/uid on www.qmail.org.
It is bases on the users/assign file (in /var/qmail/users/assign). This
files tells qmail where mail to a certain user shall be delivered too (thus
overiding /etc/passwd). This together with the virtualdomains files gives
you excellent support for a _lot_ of domains and a _lot_ of users. Note that
(as far as I remember) the user/assign file is _compiled_ into some sort of
binary file, so it should be fast also with a lot of entries.
I am using this setup, and things are quite fast. I still have a .qmail file
for each user in his directory (/home/popuser/$DOMAIN/$USER), because you
need this for forwarding, starting mail notifying scripts, etc. But if you
just want to deliver to his Maildir/Mailbox you donīt need those .qmail
files.
I have writting a small webinterface for the administration of this (you can
add domains, add users to domain, set their pop-password, add forwards to
users,...). It is a quick and dirty hack (itīs a bunch of shell scripts!),
but it works for me - you can have it, if you want to (maybe you want to do
the necesary perl rewrite?? ;-)))) )
greetings, Florian Pflug
