Comment 29 for bug 9870

Hello enveryone,

I'm surprised by this bug and it's "severe" qualification. I do use Evolution/spamassassin since 4 years now, and it's alsways been fully efficient, once I had correctly set it up, of course.

Remember you have to:

- set up spamassassin the way you want ut to work: as a resident service (spamd), or as a command-line called by evolution (as I do)? Which mail quotation will mark it as a spam? Should some foreing languages be considered as spam by default (probably the languages you don't speak...)? Do you want to use some complementary filters such as Pyzor and Razor insisde spamassassin?
- tell Evolution that you WANT it to move your spam in designed folder: excuse me if the name of the command are a bit different (I do use Evolution in french). In Evolution 2.10.1 (an other recent versions), it's become very easy: just try Edit/Mail filters, ad a test (and precise the condition: "the mail is a spam"), action to do: "move the mail to folder XXXX").
- enshure the firts time thact spamassin is correctly called when I receive your mail (under Linux: try the commande-line "top": the spamc or spamd process should be working and using a significant part of the processor time).

On my computer, Evolution calls spammassin in command-line (advantage: low resident memory loose; incovenient: it's slower). I activated every options, and so mail checking is quite slow. But the result is great: about 200 spams a day correctly designed an moved to the spam folder, no false positive. Only one false negative (then, I must check it 'spam') a week!

PS: please forgive the poor english of a french Linux lover who doesn't trains it's English regularly...