"Jesse Guardiani" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >> Once this is added to Auth.py so it is able to set the HOME >> environment variable correctly so that '~' expansion works >> properly, is there anything else necessary for virtual users to >> work? > > Hmmm... there is something nagging in the back of my head that > tells me that it isn't quite so simple... > > For instance, say you have two domains: > > mydomain1.com > mydomain2.com > > And EACH domain has a user named 'billybob': > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > Which user will ~billybob refer to? > > I'm all for it personally, but I'm having trouble making my > mind jump through the necessary hoops to understand how we/you might > implement it.
Well, according to tmda-ofmipd (off which I am basing most of the new Auth.py), the "vhome script" takes two arguments: the username and the domain, and returns the resulting home directory. If I'm reading the code correctly, tmda-ofmipd requires that a username used for logging in for a virtual user be [EMAIL PROTECTED], not just billybob. tmda-ofmipd also checks the domain part of this login username against qmail's virtualdomains file, but I don't know if this is necessary. Any thoughts? This raises one more question: Does the authentication mechanism then (whether it be file, checkpassword, or remote) expect that the username passed to IT is [EMAIL PROTECTED] I'm going to assume for now (unless told otherwise) that this is what it expects because I don't know what else would make sense. -- Jim Ramsay [EMAIL PROTECTED] _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
