Re: Migrating from SpamAssassin to Bogofilter

On Mon, 2013-06-10 at 16:41 +0100, RW wrote:
> If it's kept it should be aimed at power users. 

That's a fairly selfish view and one I've strived to avoid in the
authorship of every piece of software I've ever worked on.

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

It isn't my question.

> 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.

There isn't a reason to have to do that. If it was written properly, it
would register on either the system or session bus, a client would
attempt to connect to the service, connectivity equating with
availability of the daemon, and the messages passed through methods on
its registered interface and signals emitted when need be. All of this
can be done in a fraction of the amount of code that it currently is
dependent on. As he already pointed out, DBus solved this problem a
decade ago.

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

No, it's not primarily a library. If you want to characterize it based
on where the bulk of the code is, that's fine, but not meaningful.
That's like saying Eye of Gnome is primarily libpng or Evolution is
primarily kernel drivers.

In any case, my OP concerned migrating SA databases to Bogofilter and
not last ditch efforts to find reasons to salvage SA's anachronistic
design decisions. If you want to persist with the latter, start a new
thread and please leave this one alone.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

_______________________________________________
Bogofilter mailing list
[email protected]
http://www.bogofilter.org/mailman/listinfo/bogofilter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAlG3bFMACgkQLXnfK7bii20OeACfbJNnGcBgukOWKn2BNIN7H8Cj
sUYAoIB2yNRIQKdSjLaMY4mLRjnKZLJh
=cntG
-----END PGP SIGNATURE-----