Florin, > I'm interested to know if by default this patch has been integrated > into new fork of amavisd-new.
The one which allow to use sql_prefs for spamassassin instead of defined score in amavisd.conf.
Which patch are you referring to? Using the SpamAssassin's PMS->get_required_score from amavisd doesn't play well with amavisd's handling of per-recipient score thresholds. Amavisd traditionally calls SpamAssassin only once even for multi-recipient messages, then does per-recipient handling by itself. Using the required_score would require calling SA once for each recipient. The version 2.7.0 of amavisd went ahead in this direction and allowed calling SpamAssassin once for each recipient, and using SpamAssassin's user preferences SQL lookups. This comes at a cost, both in speed and in memory, as saving and restoring SpamAssassin state is rather expensive. Still, even with such a setup the required_score is currently ignored. So a short answer is: no, using required_score from SpamAssassin's SQL lookups is currently not practical. Mark
