Robert Senger via Postfix-users skrev den 2023-06-29 17:21:
...
The point is that spamassassin needs to know the username when
processing an email, to update the correct bayes database. The username
given to spamassassin by spamass-milter is the email address of the
recipient. This is fine, as long as an email is sent to the (real)
virtual user. But for any email sent to an alias, spamassassin gets the
alias address rather than the (real) username, and creates bayes
databases for every alias or evan wildcard address, which is not
desired.
...
i have solved this with in amavisd policy sql one policy pr recipient
mailbox, and virtual_alias just pointing to the same policy user in
amavisd, this is first step :=)
next is to in the policy define sa_username in policy table what
spamassassin username to use for this policy, it works for any username
in spamasassin so make it right without any overrides of secrets.cf
if awl bayes txrep have override its used as global trained data, not pr
user
but yes i think spamassassin can evaluate postfix virtual_alias aswell
so it knows where to load bayes and awl, txrep from in sql or even ldap
more help needed ?, just ask
using it with postgresql here
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
