361738 - Possibility to use spamassassin instead of Thunderbird's bayes integrated spam filter.

Status: RESOLVED DUPLICATE of bug 290237

(Thunderbird :: General, enhancement)

Description

[Hans Muenchen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1) Gecko/20061010 Firefox/2.0

Well the situation is that Thunderbird only use a bayesian Filter. For normal Spam it works maybe good but in the last time I saw more and more that spammer use pictures as Spam.

The solution is to use an combination of a normal antispam tool and OCR.
Because Thunderbird don't use this I integrated OCR into SA and that works good for me. But unfortunately it's not possible to use SA together with Thunderbird.

So a big wish for a future release will be that the User can choose between the integrated filter and spamassassin.

Would be great it that would be possible for example linke in Evolution or Sylpheed-claws GTK

Reproducible: Always

Comment 1

[Wayne Mery (:wsmwk)]

Are you requesting support of SA that runs server side?  Or client side?
What aspect do you find lacking in TB version 2?

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

SpamAssassin is used by a MTA or as Proxy. In all these cases a MUA only can analyze the message headers set by SpamAssassin. And this was integrated a long time ago.

Comment 3

[Kent James (:rkent)]

I don't really agree that bug 290237 accomplishes all that is possible in replacing the internal Bayes filter with SpamAssassin, so I don't agree with the dup. I would interpret this bug to request running SA at the client level. Then at the very least, we could really make the spam processing "plugin" capable of being seamlessly replaced with SA by an extension. At the most, we would maintain SA as a checkable option for spam processing instead of the existing bayes filter. I think the latter is what was requested by the reporter.

What does that accomplish over the existing analysis of bug 290237? Well for example you could replace TB's bayes processing with SA's bayes processing, including the appropriate UI to allow marking messages as spam or ham. SA bayes typically runs only at the server level mainly because of lack of integration of message classification into clients.

Comment 4

[Wayne Mery (:wsmwk)]

The reporter's address is dead, so absent information from the reporter I'm inclined to agree after re-reading comment 0 the bug as written is a dupe.  If there are areas lacking wrt Spamassassin I suspect it would better to open new bugs.