yyyyspamassassintaintorg justin mason trimmed cc list daniel quinlan said 1 messages could end falsely incorrectly reported razor dcc pyzor etc certain rbls dont think results distributed tests trusted way shape form running public corpus ill note readme 2 messages could also submitted projects like spamassassin rely filtering results submission ga tuning development second problem could alleviated somewhat adding nilsimsa signature similar masscheck file results format used spamassassin giving message files unique names md5 sha1 file ok maybe rewriting messageids help allow us pick ill 3 spammers could adopt elements good messages throw filters course theres always progression technology spammers nonspammers third problem doesnt really worry nah neither problems perhaps others identified unique spam filtering compression corpuses performancerelated corpuses set problems course words dont think theres replacement multiple independent corpuses finding better ways distribute testing collate results seems like viable longterm solution im glad working exactly spamassassin youre going seriously work filter development building corpus 1000050000 messages half spamhalf nonspam really much work dont get enough spam creating multitechnique spamtraps web usenet replying spam pretty easy doesnt get thousands nonspam every week yep primary reason released provide good big corpus academic testing filter systems allows results compared filters using known corpus spamassassin development everyone maintain corpus j thu 10 oct 2002 131423 0100 sadev fullypublic corpus mail available