On Fri, 2010-01-22 at 13:57 -0500, Charles Gregory 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? Martin
