#Spamsieve score code#

#Spamsieve score code#

So the crontab code ends up looking like this: The solution was to force ownership back to reality after each training session (which is done overnight via a cron job). For some reason, ownership of at least one of the bayes data files (nominally spampd.spampd) would mysteriously change to root.root, killing the filtering.

That worked great for a few days, then mysteriously stopped. # ll -a /home/spampdĭrwxr-xr-x 2 spampd spampd 4.0K Nov 3 20:51 awl/ conf file and symlink from /home/spampd/.spamassassin back to /var/cache/spampd/. The only workable solution was to use the bayes_path /home/spampd/.spamassassin directive in the. conf some code would default to /home/spampd/. conf file, some code was going to use /var/cache no matter what, and absent a specific directive in. After hundreds of iterations, I realized that some code was going to follow the. That seems to work at first, but somehow, somewhere, some versions of the files end up back in /var/cache/spampd/ and filtering then stops working. I’m nervous about just using /var/cache/, though, so I tried editing /etc/nf to add: bayes_path /home/spampd/.spamassassin The documentation implies that it should keep the bayesian data in the /home/spampd/ directory, but the files actually end up in /var/cache/spampd/. I run spampd as its own user (cleverly, spampd). I’m running under Ubuntu, but any Debian branch should work the same. The problems turned out to have to do with where the files were placed, ownership, and permissions-the usual suspects. I finally made a concerted effort to get Spamassassin, spampd, and Postfix playing nice together with bayesian filtering on. And the total volume of spam (including dangerous phishing and malware-carrying spam) was just out of control. I’ve been traveling a bit more, and have had to access mail from mobile devices when my laptop wasn’t able to run and do the filtering. I realized that other users on my mail system weren’t making use of their own local spam filters, and thus were getting inundated with spam. I didn’t run Spamassassin’s bayesian filter because SpamSieve did such an excellent job, and I could never get Spamassassin’s filter to work properly. I then ran the most-excellent SpamSieve on my laptop to catch the spam that Spamassassin missed. For the last decade or two, it’s been Postfix with Spamassassin (invoked via spampd) for spam control. have been running my own mail server for an eternity.managing Let’s Encrypt wildcard certificates.spamassassin + spampd + bayesian filtering.remote authentication for whole disk encryption.