OK gang. I've tested tmda-ofmipd's IP-based domain support in a semi-production environment.
We had a bug at first with IMAP authentication (sending actually, but it only happened with IMAP auth enabled), but that appears to be fixed. LDAP so far remains untested. Otherwise, it appears to be working code. I actually took some time to compare the patch against the original with 'vimdiff' yesterday. I think the implementation is pretty solid too (for what that's worth coming from a Python newbie and a mainly proceedural programmer). So, I have two questions at this point: 1.) Tim, do you plan to submit the new IP-domain code to CVS, or wait for some more testing? 2.) What are everyone's thoughts on turning this mainly tmda-ofmipd virtual domain code into a module that all TMDA apps can use? I'm personally anxious to see tmda-cgi become virtual domain capable, as it's the last piece of the puzzle before my company can begin implementing TMDA in a non-beta environment. I swore I wouldn't implement qadmin-tmda in a production environment after browsing the code and dealing with the install process. -- 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
