Gre7g Luterman <[EMAIL PROTECTED]> writes: > Although I agree that actively maintaining a whitelist is effective > with the current software, I still think that a better, more forward- > looking plan involves changing the technology to cope with that > situation.
Handling other TMDA messages is easy because the format is controlled and understood, but should it try to automatically cope with all the one-time address schemes out there? That seems like an enormous amount of work for relatively little gain. The benefit of FAQ 4.5 is that it works with any and all one-time address schemes. > It's not a big deal for me to pop open an SSH terminal and edit my > whitelist, but I currently have two users who know nothing about SSH, > Linux, BASH, and CLI's. I could possibly train them to do these > things themselves, but what happens when there are 100 TMDA users on > a server? A 1000? My grandmother? TMDA "whitelists" are flat text files with a simple and easily understood format. You could just write a simple CGI script for your webserver that lets users read/write their whitelists. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
