David Reta wrote: > > I am running spamassassin 3.1.5 which is being called from mimedefang. > I am using bayes over nfs which is shared between 2 mail relays. > Not that it's causing your problem.. but Ouch. Why share over NFS? use a mysql database, you'll get substantially better performance, and fewer opportunities for database corruption. > > We have been having some issues with some spam getting through. I did > some investigating and found out that the spam that is getting through > is not running the bayes test. Even if nothing in the bayes database > is found shouldn’t at least BAYES_00 show up? > > Do you think maybe that the bayes might be timing out? If so how can > the timeout be increased. Any ideas will help. > No, there's no such thing as a bayes timeout that would affect message scanning. Autolearning, yes.. scanning, no. > > Here is the output of the MSG.0 file from the quarantined message. As > you can see the bayes test is not run. I ran the message manually as > the same user that runs mimedefang which is shown right after and the > Bayes test is run. >
In general, your problem sounds very much like the two runs are getting their bayes DBs from different spots. Be sure to check mimedefang specific files like sa-mimedefang.cf for explicit bayes_path declarations. If there is one, it will cause mimedefang to use a different bayes DB than any other SA command-line tools are using, as they will not parse this file. Put your site-wide configuration options in local.cf, not sa-mimedefang.cf
