http://bugzilla.spamassassin.org/show_bug.cgi?id=3417
------- Additional Comments From [EMAIL PROTECTED] 2004-05-27 14:49 -------
>You can look this up yourself. Follow the link to collated results from
>the hacking on SpamAssassin web page.
Thank you for intresting link!
>I don't mind answering questions, but I need to be clear, your MX rule
>is not going into SpamAssassin. This is my last comment on this bug.
Thank you for your time!
First, I am going critisize your criteria, Can I?
I think, If we will critisize something, this will be better by the time.
Your criteria is very strong.
All hams rules can be forged by spamers. All of them.
AWL could be forged by checking active state of email accounts.
BAYES rules can be forged by sending anekdots or japan hoku.
SPF and my rule can be forged by seaching "right" emails.
To perform your criteria you should delete all ham rules right now.
But I think you strategy to reject ham rules is wrong.
I think ham rules with R/0 more than 0.25 are good and can be usefull
IMHO If we will have 100 uncorrelated ham rules with 0.25 R/0 ratio with big
Hit Rate - they create strong effect. This is mathematical fact. I am not going
prove it. Trust me.
Now I am going show that many rules from stable version do not hit your
criteria.
For example let see at ham BAYES rules and user "jm", that have ham=spam in
corpus.
R/0
44.692 1.0003 88.3846 0.011 0.82 0.00 BAYES_00:jm
0.138 0.1875 0.0875 0.682 0.44 0.00 BAYES_05:jm
0.213 0.2626 0.1625 0.618 0.42 0.00 BAYES_10:jm
0.225 0.4126 0.0375 0.917 0.36 0.00 BAYES_25:jm
There are no ham BAYES rules that perform your criteria R/0 < 0.001
R/0
0.011 more 0.001
0.682 more 0.001
0.618 more 0.001
0.917 more 0.001!
My rule have R/0 about 0.05, but you are reject it.
SPF_CHECK
0.700 0.6002 0.8002 0.429 0.38 -0.00 SPF_PASS:jm
0.429 more 0.001
I did't find AWL rules.
So.. why we use ham BAYES rules?
Are there people that dont said "this is my last comment"?
Dont trust intuition! Trust mathematical formulas!
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
