Antony Stone writes > Check the user which spamc runs
Thank you for this! root@tagol~# ps axf | grep spam 789246 ? S 0:00 \_ spamd child root@tagol~# ps axf | grep spam 662102 ? Ss 0:00 gpg-agent --homedir /etc/spamassassin/sa-update-keys --use-standard-socket --daemon 778204 pts/20 T 0:00 \_ emacs -nw /etc/spamassassin/local.cf 790063 pts/20 S+ 0:00 \_ grep --color=auto spam 789238 ? Ss 0:01 /usr/bin/perl -T -w /usr/sbin/spamd --pidfile=/run/spamd.pid --create-prefs --max-children 5 --helper-home-dir 789245 ? S 0:00 \_ spamd child 789246 ? S 0:00 \_ spamd child for better or worse it seems it's running as root. > as and ensure that this user can read the file > which is symlinked to. > > Testing stuff as root can be misleading. Sure. I also tested spamasssin from a completely plain vanilla user $ spamassassin --lint Jan 5 19:15:42.326 [792794] warn: config: failed to parse line in /etc/spamassassin/88_mailman_members.cf (line 1248): wlcomelist_from kric...@openlib.org -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21399th day.
