On 2/8/22 11:33, Kevin A. McGrail wrote:
Auto learning is something that should never of existed. All it does is
reinforce misclassification and slowly spirals the database into having
wrong answers be more wrong.
I don't agree - I've been running autoloearn for years and my bayes
results have always been solid.
(and I'm speaking of a global bayes redis DB in a 200k user setup)
Where I see potential is in optimizing auto expiration when using a file
based DB. Very often DB is locked and tokens cannot be expired which
leads to what you call "reinforce misclassification". If tokens are
expired regularly, skewing is very improbable.
Thankfully, using Redis, it's way more controllable.
Since we don't seem to have consensus on changing the default does anybody
object to a pre-file that disables it? That would be more clearly
documented in people will look at the pre-file for V4.
I'm -1 for disabling, one way or another.
Regards, KAM
On Tue, Feb 8, 2022, 04:43 Giovanni Bechis <[email protected]> wrote:
On 2/7/22 20:03, Henrik K wrote:
On Mon, Feb 07, 2022 at 06:32:18PM +0100, Giovanni Bechis wrote:
Hi,
as per Mail::SpamAssassin::Conf(3), bayes_auto_learn defaults to 1/true.
Is anybody against changing its default value to 0/false on trunk (aka
SpamAssassin 4.x) ?
What is the reasoning for this proposal?
IMHO using autolearn without a correct learning process frequently poisons
bayes data, I think bayes_auto_learn should be enabled only if you know
what you are doing and not by default.
I understand that changing a default value now could be a problem for
users.
Giovanni
