On Thu, Sep 21, 2000 at 10:41:46AM -0500, dG wrote:
> course I have to fight the temptation to ask such a lame question to the
> list, instead choosing to burn my brain cells. ;)
Waahoo! Excellent! :)
> One thing I do not fully understand is what the purpose of having the
> /user/assign (include, exclude) files is, unless one is hosting for virtual
> domains or multiple email addresses per user. Then again maybe that is the
> purpose.
That's pretty much it. In those cases it's great. If don't need to
override /etc/passwd controlled delivery you don't have much need for
it.
That said, there is a tiny gain in using it, as qmail-local will always
see if users/assign is being used. If it's not, that check is wasted. If
you have a large userbase, it could be useful if even just to replicate
/etc/passwd delivery.
That's what we do now. I use the attached makefile to try to keep
things sane.
ATB,
james
--
James Raftery (JBR54) - Programmer Hostmaster - IE TLD Hostmaster
IE Domain Registry - www.domainregistry.ie - (+353 1) 706 2375
"Managing 4000 customer domains with BIND has been a lot like
herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
# Makefile to manage qmail's users/assign mechanism of local delivery
# control. See README.
# James, 22nd May 2000.
default: cdb
# Make users/assign if with the passwd file or list of additional
# instructions has changed.
# qmail-pw2u replicates /etc/passwd into users/assign
# users/append is a list of extra assignments
assign: /etc/passwd append exclude
/var/qmail/bin/qmail-pw2u < /etc/passwd > assign
chgrp qmail assign
# Build users/assign into the CDB database format.
cdb: assign
/usr/local/bin/assign-lint ./assign
/var/qmail/bin/qmail-newu
chgrp qmail cdb
