From: Nick Gilbert [mailto:[EMAIL PROTECTED] > > I've just noticed that if I run: > > spamc -u [EMAIL PROTECTED] < spam3.txt > or > spamc -u nick < spam3.txt > > I do NOT get the bayes results which I DO get if I run: > > spamassassin -t < spam3.txt. > > So perhaps the source of the problem is not simscan after all? Why > would spamassassin and spamc produce different results?
I never said the problem was with SimScan. The problem was that you were not testing the same way SimScan was running. The first step in testing is to make your test environment match your production environment as closely as possible. If the same command is giving different results, then the environment is not the same and you need to take a close look at both sides to determine what is different. Once you can reproduce the same results on both sides, then you can start evaluating whether those results are correct. Matt Kettler asked the relevant question. Are you logged in as Nick when you are testing spamassassin? Also, are there any extra options on spamd that could affect how it finds the user information? Bowie
