On 23/01/2010 20:25, Martin Gregorie wrote: >> The only thing I can picture, technically, is a kind of auto-whitelist, or >> a user-specified whitelist. >> >> The former is subject to various pitfalls, as I've already experienced on >> my system, and the latter, even though available to the user as a post-SA >> filtering option, tends to get ignored by 95% of users. So the extra >> effort to inject a per-user whitelist mechanism into the MTA would seem to >> be a waste of time. >> >> I'm all for 'reasonable' suggestions, but they really do need to be >> 'reasonable' in the context of the user base. :) >> > Store user linked whitelist URLs in a relational database. Use an SA > plugin to apply them. Provide a GUI tool with a really simple interface > to allow users to maintain their own whitelist and blacklist entries. > Using a relational database to store the lists makes it simple to > distribute a GUI tool that's capable of being run remotely on user's > desktops and should give good comparison performance. > > Would something along those lines meet your user-friendliness criteria?
If your mail server has address book functionality, then you can use that as a whitelist. I wrote an application for doing it with CommuniGate Pro: https://secure.grepular.com/CommuniGate_Pro_Contact_Folders_as_a_Whitelist_Source_for_Exim I also add recipient addresses to a MySQL based whitelist on my MSA (Exim): https://secure.grepular.com/Whitelist_Recipients_in_Exim -- Mike Cardwell : UK based IT Consultant, Perl developer, Linux admin Cardwell IT Ltd. : UK Company - http://cardwellit.com/ #06920226 Technical Blog : Tech Blog - https://secure.grepular.com/ Spamalyser : Spam Tool - http://spamalyser.com/
