Gabriel Millerd wrote:
In v3.2 it seems the reading of the /etc/mail/spamassassin/*.(pre|cf) files is less forgiving. You used to be able to have the all in one .cf file before v3.2. Likely your header rules are in a .cf file and the sa-update is just reading the .pre file.
You could never put your loadplugin lines for plugins included with SA in cf files (in your local site config dir) without screwing up rules included with SA that depend on those plugins. 3.2 makes this breakage more visible due to a missing Check plugin causing SA to abort.
I had to juggle the /etc/mail/spamassassin files around quite a bit to get both spamd and sa-update to work. "script -c "sa-update -D" /tmp/sa.log" is your friend.
Properly configured (loadplugin lines in pre file(s)), you shouldn't have to juggle anything around.
the "\d+_scores.cf" rules also can be a pain with sa-update which is a big part of the juggling.
Care to elaborate? Daryl
