spamassassin issue since upgrade

snIP3r · l33t Joined: 21 May 2004 Posts: 853 Location: germany

hi all!

since latest update of spamassassin to spamassassin-3.4.1-r13 i have an issue with my user prefs. they worked without problems till update. no config files are changed. and now i get a message like this with every mail beeing scanned:

NTU · Apprentice Joined: 17 Jul 2015 Posts: 187

Try this:

figueroa · Posted: Fri Sep 01, 2017 5:23 pm Post subject:

I had been running spamassassin ~x86 like forever, but the recent upgrade from spamassassin-3.4.1-r12 to spamassassin-3.4.1-r13 caused BAYES to stop working. I removed the ~x86 setting in /etc/portage/package.keywords and after the downgrade to spamassassin-3.4.1-r8 BAYES works fine again.

That never happened before.

spamassassin-3.4.1-r13 is no longer available, replaced by version r16 (which also won't use BAYES), and version r8 is stable for x86.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

Philippe23 · Posted: Sun Oct 29, 2017 1:37 pm Post subject:

Submitted a bug: https://bugs.gentoo.org/635790

Philippe23 · Posted: Sun Oct 29, 2017 1:42 pm Post subject:

If you're having this problem with -r16, can you try changing /etc/init.d/spamd to remove the --username and --groupname args from command_args:

Philippe23 · Posted: Sun Oct 29, 2017 1:50 pm Post subject:

figueroa · Posted: Sun Oct 29, 2017 6:01 pm Post subject:

figueroa · Posted: Sun Oct 29, 2017 6:28 pm Post subject:

YES, by removing the --username and --groupname arguments from /etc/init.d/spamd BAYES is again working.

What are the implications of this situation?

ADDED: Thank you!
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

Philippe23 · Posted: Sun Oct 29, 2017 8:17 pm Post subject:

Pre-r16 didn't have the args, so it just puts you where you were.

There's an argument to be made that having spamd run as the spamd user would allow you to reduce access of the process, but you'd have to fixup the permissions of your $HOME/.spamassassin/ folders so the spamd user would be able to read/write to the folder for all your users (as well as modifying /etc/skel so it would have the permissions right for future users).

If you've got spamassassin setup to store user_prefs & bayes in a DB instead of the file-system, there's you're better off running as the spamd user. But if you're in this post, you probably aren't setup with a DB backend. :wink:

Philippe23 · Posted: Sun Nov 05, 2017 8:49 pm Post subject:

Update. 3.4.1-r19 fixes the above by adding a SPAMD_RUN_AS_ROOT flag to /etc/conf.d/spamd that you can enable if you need to continue running spamd as root so it can setuid to access the files in user's home folders.

As mentioned above, if your user config & bayes are in a database, you don't need to set the flag and should leave the default which will run the spamd process as a spamd user who has minimal permissions.