Checking for a while the behaviour of this, I found at the maillog that there was a message that said:
mail mailscanner[3204]: SpamAssassin timed out and was killed After googling for a while, I found that this could be caused by not enough RAM on the server. I decided to increase the RAM and test again. No difference: spam still got high score and was marked as "not spam". I decided to increase the spamassassin timeout from the mailscanner.conf file, from 90 to 300 (which I think is quite long). After that, spam started to be stored on the spam folder and it seems to be working for now. Now the question is this: Why did the time to check a message increased? Does it has something to do with how many rules are checked per message? Does this means that I should delete some .cf files? Any opinion will be important. Thanks, Edo ----- At 10:33 AM 6/23/2004, Eduardo Bejar wrote: >Hi, > >I still can�t find any solution for this. I tried google, and the list >archives. All spam gets high score but the SpamCheck says it�s no spam. > >SpamCheck: not spam, SpamAssassin (score=79.804, required 5, <snip> >Any clue will be very useful. Hmm, that's strange and something I've never heard of before. Can you provide any information about your setup? (SA version, tool that's calling SA, etc)
