Quote:
Originally Posted by tambo
Based on testing that I've done with this and other boards, the false-positive rate is a little too high (somewhere in the region of 20-25% of all flagged email/IPs). These figures were ascertained by conducting a cohort study where we tested people's IPs/emails and allowed them to register anyway, extracted the logfile, then followed them to see if they were ultimately banned for spamming. Obviously, your mileage may vary according to your users, but that is our experience.
If we implemented this mod on a reasonably busy board (100-150 registrations per day), we would expect to have a significant number of genuine people denied registration to our site. While the benefits may lead some to conclude that it's a sacrifice worth making, I'm a little less willing to break more eggs than necessary when making this omelette.
As a matter of good 'customer service', we would be prepared to whitelist IPs and emails from people who got in contact with us, then instruct them to try again.
I realise that others have suggested manually creating user accounts for people who fail the SFS check, but on a busy board that would eat up any labour-saving efficiencies that this mod brings. It's also impractical to be disabling and re-enabling the mod to permit people to get through.
I'm not the only one asking for this, which leads me to believe that either we're all misunderstanding the nature of the mod or that we're all seeing a fairly obvious gap - as did the original author when coding for v0.7.
|
the problem is if you think there are false positives, then report them to their DNSBL provider, the IP address can be removed but it takes 24hr to propagate for removal
this mod is not responsible for the false positives, its the users reporting them to SFS