Kevin Buzzard <[EMAIL PROTECTED]> wrote:
So it seems to me that the _key_ issue here is: are razor, pyzor, dcc making
mistakes with the _same_ emails?

Not from what I can see. I posted some stats from my own server two weeks ago in the "Razor2 vs DCC vs Pyzor" thread. I only compared Razor and Pyzor, because I wasn't using DCC at the time.


In that time Razor hit ~3200 messages, Pyzor hit ~2850, and ~1500 were overlaps. So roughly half of messages listed in each database were unique to that service.

Of those 1500 overlaps, only one message scored below 5.

Does anyone know enough about
the decision processes going on in more than one of these systems
to be able to state confidently that the chances that errors will
be made are essentially independent?

It's as independent as the people reporting to them. If every single person used all three to report the exact same email, then there would probably be no difference. As long as a significant number of people only report to one or two of them, the databases will trigger on different sets of mail.


I raise this question here because I have no idea of the algorithms
razor, pyzor and dcc use. I'm basically asking "are they the same"?
e.g. are they all using spamassassin with razor,pyzor,dcc turned off? :-)

The algorithm is this: Someone reads their mailbox, says "This is spam!" and reports it to Razor, Pyzor, or DCC. Razor in particular repeatedly makes the point that no mail should be reported based on automatic filters.



Kelson Vibber
SpeedGate Communications <www.speed.net>




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to