Howdy list, I've been working a lot with qadmin-tmda lately. qadmin-tmda calls tmda-pending for much of it's pending queue functionality.
One thing I noticed is that when a message is released (and maybe when a message is deleted too), tmda-pending actually pipes the message through the sendmail interface instead of doing the work directly. I can understand the advantages behind that method of doing things. It certainly makes the code a bit cleaner. But it also makes writing a GUI a bit difficult. The messages continue to linger in the maildir until tmda-filter finishes parsing them. And depending on the mail server load, this could be quite some time. Would anyone object to the abstraction of this functionality (release and delete) into a different class or having tmda-pending call tmda-filter directly? Fishing for the best solution at this point. -- 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
