Gre7g Luterman wrote: > On 22 Jan 2003 19:56:32 -0600, Tim Legant > <[EMAIL PROTECTED]> wrote: >
<snip> > 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'm not so sure about that. It may be what you plan, but that doesn't necessarily mean it NEEDS to be in there. > I want tmda-cgi to > eventually become the tool for all basic TMDA needs and that includes > cleaning up old pending files. Again, if you want to do this, then fine, but it adds a bit more complexity that is, although perhaps arguable, not absolutely necessary. I've created a Perl cron script that works just fine on the system level for vpopmail, and making one for VMailMgr wouldn't be too hard either. But if you DO choose to implement this functionality, you MUST provide a way to lock this down at the system administrator's request so that systems with limited disk space won't be overrun by pending emails. If you're comfortable with that added level of complexity, then have at it. In addition, obviously there could be different levels of providing a way to "lock this down at the system administrator's request". You could provide a simple "do not let any users modify cron jobs" switch, or you could take it any number of steps further by allowing the sys admin to specify which domains can modify cron jobs, which domain admins, which users's, etc... > 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. I haven't heard from Tim in a while. I wonder what he's up to, and if he ever plans to finish the migration and integration of virtual user code into the ~ expansion routines like he said he wanted to. That would certainly make your job a good bit easier. You could then treat virtual users just like system users, but I'm not sure that it's really an implementable idea. How would you deal with overlapping system and virtual user accounts? I personally think that due to the nature of programs like tmda-ofmipd and tmda-cgi it makes more sense to simply include a standard virtual domain library that these programs can query when they need to accomodate virtual users. > > Gre7g. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net We are actively looking for companies that do a lot of long distance faxing and want to cut their long distance bill by up to 50%. Contact [EMAIL PROTECTED] for more info. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
