http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5270
------- Additional Comments From [EMAIL PROTECTED] 2007-02-12 11:10 -------
well, it wasn't just that. still seems broken; a really good rule like
RCVD_FORGED_WROTE gets a score of 0. I've fixed the bugs that had marked those
rules as immutable with a score of 0, but even so, the perceptron is setting
their evolved score as 0...
: jm 135...; grep RCVD_FORGED_WROTE gen-set2-2.0-4.625-100/freqs
9.376 14.6938 0.0000 1.000 1.00 0.00 RCVD_FORGED_WROTE
9.348 14.6504 0.0000 1.000 1.00 0.00 RCVD_FORGED_WROTE2
0.000 0.0001 0.0000 1.000 0.51 0.00 T_RCVD_FORGED_WROTE3
: jm 136...; grep RCVD_FORGED_WROTE gen-set2-2.0-4.625-100/scores
score RCVD_FORGED_WROTE 0.000 # [0.000..4.162]
score RCVD_FORGED_WROTE2 0.000 # [0.000..4.162]
: exit=0 Mon Feb 12 19:07:29 GMT 2007; cd
/export/home/jm/ftp/spamassassin/masses
: jm 137...; grep RCVD_FORGED_WROTE gen-set2-2.0-4.625-100/test
: exit=1 Mon Feb 12 19:07:35 GMT 2007; cd
/export/home/jm/ftp/spamassassin/masses
: jm 138...; grep RCVD_FORGED_WROTE gen-set2-2.0-4.625-100/log
: exit=1 Mon Feb 12 19:07:38 GMT 2007; cd
/export/home/jm/ftp/spamassassin/masses
: jm 139...; grep RCVD_FORGED_WROTE gen-set2-2.0-4.625-100/make.output
rule T_RCVD_FORGED_WROTE3 no longer exists; ignoring
: exit=0 Mon Feb 12 19:07:43 GMT 2007; cd
/export/home/jm/ftp/spamassassin/masses
: jm 140...; grep RCVD_FORGED_WROTE tmp/*
tmp/ranges.data:0.0 4.5 1 RCVD_FORGED_WROTE2
tmp/ranges.data:0.0 4.5 1 RCVD_FORGED_WROTE
tmp/rules.pl: 'RCVD_FORGED_WROTE2' => {
tmp/rules.pl: 'RCVD_FORGED_WROTE' => {
tmp/rules.pl: 'RCVD_FORGED_WROTE2' => '0',
tmp/rules.pl: 'RCVD_FORGED_WROTE' => '0',
tmp/scores.data:nRCVD_FORGED_WROTE
tmp/scores.data:nRCVD_FORGED_WROTE2
I checked tmp/tests.data, and the test number for RCVD_FORGED_WROTE really does
show up in mails in the perceptron input format, too.
looks like a perceptron bug.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
