On Thu, 2010-08-05 at 14:00 -0500, Matthew Kitchin (public/usenet) wrote: > Thanks. We are looking at roughly 70,000 names and always growing. If I > gave it sufficient hardware, would you expect that to be practical, or > is that totally ridiculous? Any options for a database look up here? > I'd use a plugin that simply queries the database plus a rule to activate the plugin by calling its eval() method and sets the score if the rule fires.
I'm currently doing the reverse: - I use a view on a mail archive database to check whether I've previously sent mail to the sender of an incoming message and wrote an SA plugin to query the view. - a rule causes a plugin to query the view and whitelists the message by applying a large negative score if the query got a hit. - the plugin + view does also detect incoming messages containing my addresses as forged senders since that's a common spammer trick. This works very well. E-mail me off-list if you'd like a copy of the plugin since I haven't yet published it. However, if you're not intending to apply any other rules to the outgoing messages then using SA sounds a bit like overkill when you could simply write small program in Perl, Python, Java, etc. that simply runs the query and causes your MTA to bounce any messages than contain matches with a suitable error code or diagnostic. Martin
