On Fri, 28 Mar 2003 05:34:52 -0500, "Jesse D. Guardiani" <[EMAIL PROTECTED]> wrote:
> > 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. Well, sysadmins with virtual users using TMDA are going to want their pending directories cleaned so they don't fill up the disk. What better tool should we put this functionality in? > 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. Yup. This has been discussed already. > 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 just plan to make it so you can lock it out in /etc/tmdarc. Since the config file is Python code, the sysadmin can make the criteria for who can and who cannot change cron jobs as simple or as complex as s/he wishes. > 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. I would really like to encapsulate this sort of stuff in one central module. That would be best from a design point of view. > How would you deal with overlapping system > and virtual user accounts? I'm afraid I do not understand what you mean. > 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. Yup. We agree there. Gre7g. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
