On Mon, August 3, 2009 01:51, Steve wrote: > So a distance of 2500 Km would result in: > + 0.50 > + 1.00 > ------ > + 1.50 > > A distance of 1500 Km would result in: > + 0.50 > - 1.00 > ------ > - 0.50 > > Ach! Reading that now already tells me that most users would not be able to handle that. Better to go with the commutative approach. Or what do you think?
I tend to agree - it would probably raise more questions than users. > So you think I should take the time to quickly add the scoring by distance and scoring by continent into policyd-weight? Some admins might employ both, but I imagine that scoring by continent will be adopted by more than scoring by distance. Of course some cases will not fall neatly into either. I see a fair amount of spam attempts from Central American nations, most of which fall within the distance span of covered by most points in Canada to most points within the US, so distance filtering is less helpful, and Central America isn't a continent but a region of North America. Lets say I was providing mail services for diverse users across Canada and the U.S.; I likely would not use distance filtering to deal with South America (hello Brazil, you shimmering sun-baked source of tons of spam) but continent filtering certainly would save me from maintaining a lengthy list of country ranks including CL, AR, PE, UY and others. In my case I know I would quickly implement continent support and might later dabble with distance but suspect that continent and countries would be most helpful. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
