At 06:34 AM 1/9/00 Karl-Heinz wrote:
I dont want to let a domain owner be also the site admin. I like to manage this part myself.
We want our site-owners to be able to upload to their site using FTP. We want them to be able to see their stats. What we DON'T want is for them to be able to add users to the box. We need to control the number of mailboxes we offer, and the number of forwards we offer, with each of our packages.
Letting site administrators add users to the RaQ2 opens up a real can of worms, since each user name can only be used once. The support calls increase dramatically. We solve the problem by assigning user names and aliases. Our users get to choose their own passwords (and I'd love a place where they can change their passwords but not do anything else), but we give them both their login name (which is actually the "user name" and their email address (which is usually an alias to that login name).
Now... How to easily do that on the RaQ2?This is a must for us if we're ever to get more RaQs. I can't imagine other hosting companies don't have this same need.
Jeff
If i setup a new domain on my Raq3, i have to setup a user also, this user get his own user dir and can only access the domains html root dir, if he is also the site admin. If i allow this, he can also acess www.site.com/siteadmin If i setup a "normal" user, this user can only publish in www.site.com/~user So my question is: Is it possible to install a user via the web interface, which is not the siteadmin, but is able to publish html pages to the document root, so that this pages appear under www.site.com and not www.site.com/~user Or can this only be done by editin httpd.conf. If yes, how and are the changes permanent and to gone with the next use of the web admin?
-- Jeff Lasman, nobaloney.net <jblists@xxxxxxxxxxxxx> <www.nobaloney.net>, <www.mailtraqna.com>, <www.email-lists.com>