Alex skrev den 2020-11-10 20:30:
It also looks like there's "whitelist_from", but no "whitelist_auth"?
Or "blacklist_from"? How much work would it be to add it to the
database then configure SA to actually look for it?
this can be done in sql spamassassin, read the docs
in amavisd only whitel
> > https://cwiki.apache.org/confluence/display/SPAMASSASSIN/UsingSQL
>
> create pr user rules, set the scores default to 0
>
> in sql, then change scorees pr user, easy :=)
>
> and amavisd have sa_userprefs maps to sa_user, it's just not that easy to
> make work as intended
This is kind of what I
Matus UHLAR - fantomas skrev den 2020-11-09 14:43:
no, amavis processes all mail under single user, usually "amavis".
user prefs in sql is still supported in spamassassin even for system
users in the host
and amavisd have usermaps to sa_users, so its all supported
but the gaviat is more th
Alex skrev den 2020-11-09 14:37:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/UsingSQL
create pr user rules, set the scores default to 0
in sql, then change scorees pr user, easy :=)
and amavisd have sa_userprefs maps to sa_user, its just not that easy to
make work as intended
On 09.11.20 08:37, Alex wrote:
I'm aware of the ability to store user prefs in mysql, like whether to
use bayes or razor, but is it possible to have rules on a per-user
basis with SA 3.4.4 and amavis?
no, amavis processes all mail under single user, usually "amavis".
you probably could make ma
Hi,
I'm aware of the ability to store user prefs in mysql, like whether to
use bayes or razor, but is it possible to have rules on a per-user
basis with SA 3.4.4 and amavis?
I realize I could write a meta rule that combines a rule with a
recipient address, for example, but ideally I'd like to hav
