This is my scheme as well! Pretty much to the t. Except my HTPC is hypnotoad and nibbler is my NAS.

Ok, so I have removed all the flags and all the mods. I also shut down the upstream velocity proxy, in case it was an issue with polling the server or something. Even running by itself the consoled gets completely spammed by messages. I know that these are not errors in themselves, but spamming the console just makes catching any real errors or relevant warnings that much more difficult. As a side issue, I’m using puffer panel to manage all the worlds and installs and the spam to the console makes the admin panel unresponsive. I have no idea where to trouble shoot next.

Oh, and in case it’s relevant, I’m running the jvm with these flags (I just copied over the flags I had on my paper server): -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true

This is a 1.21.4 server.

Hey! thanks for the offer. I’ve pasted the output here: https://pastebin.com/X7Wfw9JU (this is just a fragment; the server has been on for a couple of hours and I could paste a Mb of text easily. It is very verbose)

These are the mods installed I have installed:

• fabric-api
• instantgroup
• voicechat
• worldedit
• tick-stasis
• lithium
• krypton
• cloth-config
• spark
• ferritecore
• viewdistancefix
• FabricProxy-Lite

😂

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.