Migrating from SpamAssassin to Bogofilter

[RW]

On Sun, 09 Jun 2013 11:57:06 -0700
Kip Warner wrote:

> On Sat, 2013-06-08 at 14:43 +0100, RW wrote:
> > Sidney Markowitz, the only SA developer you didn't alienate,
> > summed-up the situation with:
> > 
> >  "After all that, the only actual problem that I see is the
> > confusing error log."
> > 
> > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6939#c89
> 
>         If SpamAssassin truly is intended to be server software then
> it doesn't seem worth it to me to even keep the Evolution
> integration.  We default to and recommend Bogofilter for client-side
> spam filtering anyway....

If it's kept it should be aimed at power users. At the moment it's
getting bogged-down in the Gnome doctrine that configurability
is bad.

>         Well my general thoughts are the amount of acrobatics that
> Evolution has to do to determine whether a spamd process is already
> running or whether to launch its own and then basically invoke
> methods on it by spawning spamc and reading process exit codes is
> archaic and stupid.  It's 2013 and D-Bus already solved this problem
> a decade ago

You're begging the question: is autodetection a useful thing?

All it really gives you is the absence of a setting to select a
global spamd instance. But since there are good reasons why a user might
want to choose manually, that's a much better solution.

>         I keep hoping spamd will someday grow up and grow a D-Bus
> interface so modern mail clients can interact with it sanely.  This
> is a big part of the reason why Evolution defaults to Bogofilter.


Bogofilter can be run globally too. 


At the end of the day SpamAssassin is primarily a spam filtering
library. No one is forcing evolution to access it via spamd.