😂

Yup, this is the last time I muck around with spamassassin unless the project gets a magical revival.

I think I got it working. I’ve got this in /etc/default/spamd:

OPTIONS="-x -q -u spamd --max-children 5 -H /etc/mail/spamassassin/"

and this in /etc/default/spamass-milter:

OPTIONS="-e example.com -u spamass-milter -i 127.0.0.1"

And it definitely reads user prefs from the database because I can change the ‘required_hits’ to 6.7 for a given user and I see this in the logs:

spamd[523771]: spamd: clean message (-0.2/6.7) for user@example.com:133 in 1.2 seconds, 24427 bytes.

I don’t know how many different combinations of config flags I’ve tried, but these seem to do the job.