As an administrator with a couple of thousand tmda-protected email boxes, I would whole heartily vote for something that can be done at one time, and with the oversight of a human. Theres no reason to use some "coding magic" to automatically covert the pending queue during message delivery.
This way also, the administrator can pause mail delivery while the manual conversion does its task. I have some users that have several hundred email hits a day to the system, and potentially having another email come in starting a new conversion process while one is already happening would be painful. Should there be some coding magic to make sure the actual queue structure matches the item in the config file? Sure. Should it be changing the changing the queue structure automatically? No. As for extending tmda-pending - I would vote for a new script. I would think that the conversion process would happen once. There may be a rare opportunity for it to happen more often - but realistically how many times are you going to need to change? Putting it in a different file makes sure noobs arent fussing around with config option, and sets apart that process. In addition, its not a huge re-write to tmda-pending when new pending queue schemes are dreamed up. >I came to pretty much this same conclusion after thinking about it >some more. I think I'll extend tmda-pending with a '--convert' option >with possibly two more options for "before" and "after" formats. I >just hope this will be flexible enough for large installations, but >I'm sure we can make it so as we get more feedback. > >_________________________________________________ >tmda-workers mailing list ([email protected]) >http://tmda.net/lists/listinfo/tmda-workers --Photocon Conrad Hunziker III NightSky Hosting - http://www.nightskyhosting.com/ _________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
