On 2014.12.09 06.46, Mark Martinec wrote:
On Dec 08, 2014, at 19.28, Mark Martinec <mark.martinec...@ijs.si>
wrote:
Actually, looking at a diff of DBM.pm between 3.4.0 and 3.4.1
I can see the taint bug has already been fixed by r1608413:
@@ -814,3 +816,3 @@
my @vars = $self->get_storage_variables();
- dbg("bayes: DB journal sync: last sync: ".$vars[7],'bayes','-1');
+ dbg("bayes: DB journal sync: last sync: %s", $vars[7]);
The extra parameters shouldn't have been in that dbg call.
See:
Bug 7065 - Debug Mode breaks Bayes but only if DBM storage is used
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7065
Ben wrote:
i've manually grafted that patch onto my 3.4.0, and it seems to do the
trick, thanks. i now see bayes results [and more consistent results
overall] when using --debug.
Good, thanks for confirming!
there is still a slight variation in scoring, however:
without --debug:
Content analysis details: (19.6 points, 5.0 required)
[...]
-3.8 AWL AWL: adjust score towards average for this
sender
with --debug:
Content analysis details: (19.5 points, 5.0 required)
[...]
-3.7 AWL AWL: adjust score towards average for this
sender
all other scoring is consistent. it's a trivial variation in this
instance, but does it mean something additional may not be working as
intended? or just something else i need to learn?
That's normal, AWL scores are dynamic. Especially if you use the same
test message multiple times the AWL score would slowly shift its value.
Mark
ah, of course. that makes sense. thanks very much for the help with
this thread, and thanks to joe quinn earlier for the clue regarding
scoresets.
-ben
