Paul Arnone wrote: > Thanks. Good to know that some of those modules are optional. > > SpamAssassin was already in place on our server when I started working here. > But sometime after the old Network Admin left, it stopped flagging our > emails. > > If bayes is optional for SA, then I could change use_bayes 1 to use_bayes 0 > in local.cf and comment out the other bayes_ classifier options and it > should work? > It should work even with those options in place.
SpamAssassin normally treats configuration conflicts as warnings and just ignores them. ie: if you tell it to use a feature, but the modules aren't present, it just ignores you and disables the feature and goes on its merry way. Now, you say it stopped flagging messages.. Is it just missing a lot of spam, or is it not adding anything to any emails at all? If it's not adding anything to any emails, odds are someone made a configuration change that disabled calling spamassassin. Do you know where in your mail chain SpamAssassin was being called before? Was it in procmail, or using a milter, or some other thing? As I said before, merely having spamd running (ie: starting the spamassassin service) doesn't do anything to your email. There needs to be some part of your mail chain configured to call spamassassin, or spamc, or load the Mail::SpamAssassin perl API and feed messages to it. (and unless you're using spamc, running spamd is pointless)
