On 22 Jan 2003 19:56:32 -0600, Tim Legant <[EMAIL PROTECTED]> wrote: > Actually, the stuff in MTA is used only by the VMailMgr support. The > important code is in Util (getvuserhomedir) and in tmda-ofmipd itself > (the VDomainProxy class). As I commented in my announcement, this is > what I consider alpha level code. I wanted to get it in place and > make sure that it was working with various configurations before I > decide how to organize it in the final version. > > If the tmda-cgi guys want to incorporate these ideas, we should talk > about what they need here on -workers. I'm thinking about a VDM > support module that can be used by anyone, but I haven't arrived at a > design yet. Understanding what tmda-cgi needs from it would help.
<looks in sheepishly> Hey folks, I was just looking through the old archives and I stumbled across this thread from January. Guess I totally missed this one. Sorry about that. To be able to support virtual users, tmda-cgi needs a few things: [1] To be able to verify a plaintext password & user name combo for any user (real or virtual). [2] To know what UID the program should be running as to handle files for a given user (real or virtual). [3] A way to find out the correct home directory to use for a given user. Given that, we should be able to do what we currently do for real users, for all users. Also, although we don't need it yet, we are GOING to need to be able to find out what virtual users are on the system. I want tmda-cgi to eventually become the tool for all basic TMDA needs and that includes cleaning up old pending files. I can create cron jobs for each real user, but for the virtual users I will need to make a single cron job and have it iterate through each virtual user account. Gre7g. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
