> Russ.. did you run sa-learn --sync after you did your upgrade? > I did, and I ran it again and noticed something odd...
My config dir is /etc/mail/spamassassin My local.cf USED to have /usr/local/etc/bayes/bayes as the bayes_path, but I have since changed it to /tmp/bayes/bayes and /tmp/bayes for testing purposes. It currently has the /tmp/bayes/bayes setting. However with /tmp/bayes/bayes in the .cf file - when I run "sa-learn --siteconfigpath=/etc/mail/spamassassin --sync", it updates the datestamp on the bayes files in my old bayes location - /usr/local/etc/bayes/bayes > ls -altr /usr/local/etc/bayes -rw-rw-rw- 1 root wheel 65536 Feb 12 15:09 bayes_toks -rw-rw-rw- 1 root wheel 65536 Feb 12 15:09 bayes_seen ... and that's AFTER I've restarted spamd multiple times - even gettting confirmation with this in my log file: spamd[96453]: config: SpamAssassin failed to parse line, "/tmp/bayes/bayes" is not valid for "bayes_path", skipping: bayes_path_/tmp/bayes/bayes So my original question was: 1. What's wrong with "bayes_path /usr/local/etc/bayes/bayes" where it was working before in 3.0.x and now not in 3.1.x..." ...to ADD a new find.. using "sa-learn" obviously is messing with the files in my old location at /usr/local/etc/bayes/bayes when my config file says /tmp/bayes/bayes ... and yes, I've done a word search on my /etc/mail/spamassassin directory and there is absolutely no other instance of "bayes_path" or "/usr/local/etc/bayes/bayes" anywhere other than that once instance in my /etc/mail/spamassassin/local.cf. Baffled.
