On Fri, November 8, 2013 2:56 pm, Sergio Durigan Junior wrote:
> The problem with having a user-tailored database is that I will have to
> run sa-update for every user, right?
No, or at least, not that I've seen. If spamd is running as root, it will
load the sa-update rules from the root installation
(/var/lib/spamassassin); it will only su to the user when called by spamc,
and then it will only load that user's local Bayes DB and local rules (if
enabled); it doesn't have to load any of the main rules, which are kept in
memory from when spamd was first initiated (and were loaded from the root
installation). This is also why it's important to restart spamd when
sa-update actually updates rules (the sa-update cron script should do this
for you).
At least, this is how it works on my system, which has a pretty vanilla
install of SA.
Even if your users are running spamassassin versus spamc, it should be
able to read the rules in the root install location, as long as your users
have read permission. If you're running on a virtual host platform with
multiple chroot environments (e.g. cPanel, Parallels Pro Control Panel,
etc.) then you may need to run sa-update for each environment, but you
should still only need the one root install (and one sa-update command)
for running spamd as root.
> What's your opinion?
I would run spamd as root and initiate spamc with the -u option, to allow
each user to have his/her own Bayes DB. However, again, it really depends
on what kind of email system you're running, and how you want to handle
spam. If you're running a corporate server, you might prefer a global DB;
if you're running a server with personal users whose email characteristics
vary widely, you might prefer per-user DBs. For my setup, I prefer
per-user DBs.
--- Amir
