First of all, thanks for the quick responses. I use a small perlscript with preforked-workers that user Mail::SpamAssassin etc. The worker is spawned once at startup an then checks mails one after another without being respawned.
Can the SQL-whitelist do the trick? Is the SQL-query done at SpamAssassin startup or before each sa->check() so that changes in the sql database after startup will be included? The latter would be helpful for me ;-) With a table like this I'd be able to set a dynamic whitelist: pref | value | user whitelist_from | [email protected] | user1 whitelist_from | [email protected] | user1 ... One question comes in mind: will older pref from previous mails/users be unloaded, since there are multiple config lines for whitelist_from e.g. possible? Or will all whitelist_from lines be reset when the first "new" one is loaded from the DB? Maybe one of you guys knows this, otherwise I will check it out ;-) lots of thanks! -- Sent from: http://spamassassin.1065346.n5.nabble.com/SpamAssassin-Dev-f69836.html
