Signup abuse detection and blocking

Signup abuse detection and blocking [Paid] 1.16.11

No permission to buy ($45.00)
So I purchased this, set up the options. I see this under the IP checking, "IP matches are considered a low quality signal and will not trigger a multiple account match by themselves."

Signing up without a cookie being present on the browser does not trigger a duplicate account thread.
Apologies, I thought I remembered seeing some triggered by IP but looking at logs... it's cookie or cookie+IP.

You do have the option to look at this log ../admin.php?anti-spam/multi-accounts/. This will list multiple accounts and you can view IP data there as well.
 
Well that’s unfortunate.

So how do I configure the addon to not do any spam checks, I only want it to check duplicate accounts.
 
Well that’s unfortunate.

So how do I configure the addon to not do any spam checks, I only want it to check duplicate accounts.
Sorry. :(

You can just not configure the bottom section of the addon settings. Anything under "Content spam checking" near the bottom of the main config page. If you're really just after the multi account checking, you can probably turn down/turn off the other sections as well (Connection Profiling, etc.)
 
So how do I configure the addon to not do any spam checks, I only want it to check duplicate accounts.
You'll need to blank most of the spam check options or set them to 'accept' rather than moderate/reject (for signup checks). Then similar for the 'Content spam checking' options.
 
With XF 2.3.5, I started to get these error with latest version 1.16.8
I suspected this may have something to do with php 8.4.3
Template error: [E_WARNING] Attempt to read property "LogEvent" on false Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:196

Template error: [E_WARNING] Attempt to read property "LogEvent" on false
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:196
Template error: [E_WARNING] Attempt to read property "event_id" on null
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:196
Template error: [E_WARNING] Attempt to read property "LogEvent" on false
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:196
Template error: [E_WARNING] Attempt to read property "username" on null
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:194
Template error: [E_WARNING] Attempt to read property "LogEvent" on false
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:194
Template error: [E_WARNING] Attempt to read property "triggering_user_id" on null
Sunday at 10:58 PM src/addons/SV/SignupAbuseBlocking/Entity/ReportData.php:194
 
Are the Email Rules ordered? Or are more specific matches matched first and then the rest ignored? Something else?

For example:

+4|gad@gmail.com
+1|*@gmail.com

Does that match the first entry and then stop or will it just end up with a score of 5? I would assume the latter and then I could tweak and adjust the trigger level accordingly.

Is there detailed documentation somewhere that I haven't found?

Thanks BTW - So far this plugin has helped tremendously! Reporting dupe registrations alone have been invaluable.
 
Also, am I correct in assuming that the patterns are no RE and that only * and ? are supported as per the description?

moderate|....@ means something very different in RE than if those dots are considered literals.
 
Are the Email Rules ordered? Or are more specific matches matched first and then the rest ignored? Something else?
Yes the rules are ordered. Most of them do not stop on first match and that is something I really need to better document or add a configurable for.

Also, am I correct in assuming that the patterns are no RE and that only * and ? are supported as per the description?

moderate|....@ means something very different in RE than if those dots are considered literals.
Yes, it doesn't support regex's and only * and ? wildcards
 
Problem is, if I log into user A’s account to check permissions, then later at some point log into use B’s account, it triggers the detection as user A and B being multiple accounts.
 
Problem is, if I log into user A’s account to check permissions, then later at some point log into use B’s account, it triggers the detection as user A and B being multiple accounts.
Haven’t done that, not sure how to solve that one. @Xon may have an idea…
 
Is their any way to stop the duplicate account reporting/logging while logging in as another user via this addon, https://xenforo.com/community/resources/login-as-user-lau2.6622/

Or a ignore user cookie setting, so you could enter username’s to ignore them if they have a cookie setting.
I'll need to add support for disabling the multi-account detection for the login code-path to support that add-on. I haven't looked into what would be required to support that add-on but I don't think it would be too much effort
 
Back
Top Bottom