Fritz Borgstedt wrote: > The problem is, that the very small group of developers are forced to > waste resources in hunting these "wishlists".
If ASSP was more widely known about and accepted, there would likely be more developers interested in helping out. I only offered a thought about it, and a reason behind why people look for it. If it truly is not a viable solution, then why don't we/someone write something up about it. I'm sure a lot of people out there have no concept of why its not necessary or useful to have per-user whitelists. I am looking at this from an admin (and potential admin) perspective - not a developer who has intimate knowledge of what works and what doesn't. I participate in a number of email administration lists, and a lot of people use individual whitelists as a criteria when looking for a spam filter. Commercial or not, its a criteria that a lot of people look for because it makes sense to /them/. If its truly not an appropriate thing to look for, I think that we should try to document why. PS: My "thoughts" about it also mentioned using a triplet to specify a domain name instead of a specific user address for individual whitelisting. That way, instead of running multiple instances of ASSP to obtain per-domain whitelisting, a single whitelist could be used for multiple domain support. Could that be of use? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
