vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)
-   -   Anti-Spam Options - vbStopForumSpam (https://vborg.vbsupport.ru/showthread.php?t=230921)

tambo 10-30-2012 08:27 AM

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.

TheSupportForum 10-30-2012 06:15 PM

Quote:

Originally Posted by tambo (Post 2377000)
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

ShannonA 10-30-2012 06:31 PM

Turned this on yesterday and it's blocked over 15,000 registrations in something less than 24 hours. (I assume many of these would have been blocked already with our human verification options, but many would have gotten through too, so this is a big plus.)

However, we've also had one real user (presumably) mail us saying he couldn't create an account. So what do you do to get a real user access?

TheSupportForum 10-30-2012 07:49 PM

Quote:

Originally Posted by ShannonA (Post 2377096)
Turned this on yesterday and it's blocked over 15,000 registrations in something less than 24 hours. (I assume many of these would have been blocked already with our human verification options, but many would have gotten through too, so this is a big plus.)

However, we've also had one real user (presumably) mail us saying he couldn't create an account. So what do you do to get a real user access?

its easy to get their IP removed, first of all i can help you with that PM me and i'll send you details on how to get his IP unblocked

ShannonA 10-30-2012 07:54 PM

Great! Will do. (I'm currently waiting to get info on who he is back, so I can correlate that with the blocking info in the log.)

Ski4People 10-31-2012 04:23 PM

Quote:

Originally Posted by ShannonA (Post 2377096)
Turned this on yesterday and it's blocked over 15,000 registrations in something less than 24 hours. (I assume many of these would have been blocked already with our human verification options, but many would have gotten through too, so this is a big plus.)

However, we've also had one real user (presumably) mail us saying he couldn't create an account. So what do you do to get a real user access?

I think you should use just the IP and email check, no username check, it works for me

djbaxter 10-31-2012 04:53 PM

Quote:

Originally Posted by LukeNet (Post 2377314)
I think you should use just the IP and email check, no username check, it works for me

Yes. You will get a LOT of false positives if you enable name check.

GamerPerfection 10-31-2012 06:00 PM

I agree, only use IP and email check. never use username check.

ShannonA 11-02-2012 04:32 PM

Well, things worked great for a bit less than 4 days, then I started getting:
Quote:

Result on field email - XXXX@gmail.com [REMOTEERR] Unverfied but allowed by policy
And all the spam is flooding in again. What happened!?

TheSupportForum 11-02-2012 04:37 PM

Quote:

Originally Posted by ShannonA (Post 2377841)
Well, things worked great for a bit less than 4 days, then I started getting:

And all the spam is flooding in again. What happened!?

you need to update the api address from stopforumspam.com to api.stopforumspam.com the aapi is no longer updated from stopforumspam.com


All times are GMT. The time now is 07:46 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01449 seconds
  • Memory Usage 1,747KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (6)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (2)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete