Thomas Krichel wrote:
Hi gang,
my first post here.
I'm running version 4.0.0-8 on debian testing. This is for
Mailman. I have a script that creates a welcomelist for all my
Mailman members. I include it via a symlink.
# ls -l /etc/spamassassin/88_mailman_members.cf
lrwxrwxrwx 1 root root 57 Jan 5 15:52 /etc/spamassassin/88_mailman_members.cf
-> ../../home/mailman/opt/spamassassin/88_mailman_members.cf
Clearly spamassassin follows the symlink and reads the file. I can
see by just making a mistake in it, mistyping welcomelist as
wlcomelist
root@tagol~# spamassassin --lint
Jan 5 17:58:51.081 [783424] warn: config: failed to parse line in
/etc/spamassassin/88_mailman_members.cf (line 1248): wlcomelist_from
kric...@openlib.org
root@tagol~#
But
# spamc -R < /tmp/test.mail
Did you restart spamd after adding the symlink but before this call?
Can you find the startup log entries for the last spamd start before
this call, and see if there were any errors logged that might be relevant?
The only slightly suspect item from above is the relative symlink
starting with ../ - I would suggest remaking that symlink with an
absolute path instead. Another thing to check is if there is some
security component (Apparmor/SELinux usually, IME) active - it may
object to spamd following the symlink where it allows the "spamassassin"
script.
I don't recall ever having any issues symlinking SA configuration like
this myself.
-kgd
