| 1 |
Stroller wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> There doesn't seem to be much interest in keeping the Portage tree |
| 5 |
> up-to-date with the current releases of Bogofilter, however |
| 6 |
> development of it is moving quite rapidly & it is at a stage now at |
| 7 |
> which I believe the ebuild *should* be updated, if it is intended to |
| 8 |
> remain in Portage. |
| 9 |
> |
| 10 |
> From what I have heard of Spamassasin it uses several methods to |
| 11 |
> detect spam (including blacklists based upon the reports of other |
| 12 |
> users?), and I choose Bogofilter because it's relies purely upon |
| 13 |
> Bayesian analysis of MY spam messages. So I would like to see |
| 14 |
> Bogofilter remain current within Gentoo. |
| 15 |
> |
| 16 |
> I have forwarded below an email from Bogofilter's maintainer to the |
| 17 |
> Bogofilter mailing list giving some outlines of why I think an update |
| 18 |
> is needed at present. It's particularly worth noting that the present |
| 19 |
> version of Bogofilter within the tree (0.13.7.3) uses two separate |
| 20 |
> wordlists for spam & ham. Current releases use by default a *single* |
| 21 |
> wordlist of tokens with a pair of spam/ham counts - the separate |
| 22 |
> wordlists are depreciated, and the code will be removed in 0.17.x, so |
| 23 |
> I think Bogofilter-0.16 may be a desirable step to reduce problems |
| 24 |
> during `emerge --update`s in the future. |
| 25 |
> |
| 26 |
> If any interested &/or helpful dev could take a look at |
| 27 |
> <http://bugs.gentoo.org/show_bug.cgi?id=37017> I would be much |
| 28 |
> indebted. To give you a head-start on the New Year's bug-fixing |
| 29 |
> league-table, I think that if Bogofilter-0.16.0 were to enter the |
| 30 |
> Portage tree, this bug <http://bugs.gentoo.org/show_bug.cgi?id=31800> |
| 31 |
> could also be closed. |
| 32 |
> |
| 33 |
> Many thanks for your time & bandwidth, |
| 34 |
> |
| 35 |
> Stroller. |
| 36 |
> |
| 37 |
|
| 38 |
You could setup SpamAssassin to function in an identical way to bogofilter |
| 39 |
by weighting all other spam criteria to 0.0 points. I found bogofilter to |
| 40 |
be a pain to use and it is resource intensive. However, it has the obvious |
| 41 |
potential if it could ever be daemonized. |
| 42 |
|
| 43 |
Tom Veldhouse |
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives