Marc skrev den 2023-07-10 09:07:
https://www.mail-archive.com/users@spamassassin.apache.org/msg110390.html
lost in transaction with points of why is spamc needed when spamd provide a port 783 native socket ports just like when clamd provide 3310 on tcp, my point is valid
as with clamav i would prefer internal milter from spamassassin over spamc/spamd combo
i am now just back to amavisd-new with pr user awl/bayes/userprefs all in postgresql with roundcube sauserprefs it works pr user nicely
tip: in amavisd sql make policy in sql match mailbox in dovecot, and all virtual alias in postfix match new amavis users to use same policy if its same mailbox, this is solving pr user data in spamassassin if not wanted to be global !
in the policy sql table sa_username should match mailbox login, then spamassassin knows what user it is to use on all data in sql
old goal with amavisd is scan once, process multiple recipients, i just don't know yet if it works or not, good results from penpal's support in amavisd when sql is in use, could this be moved to spamassassin ?
