Quote:
Originally Posted by rEd86
But when the system checked, we sent all three parameters to be verified, right? (username, email address & IP Address) I would think that if one of those parameters set off a spam flag, then the others would be added to the database. So in this example, when geraldevans hit us from a spammer ip address (64.20.45.178) then their email address would be considered a spammer and added to the system. (or at least a higher probability of a spammer)
The fact that we submitted their name/email from a second IP address within 5 minutes should have confirmed that was the case.
Are there fall-outs that I am not aware of as to why one wouldn't want to be aggressive like this?
I understand how that works. I am VERY appreciative of what's been done and patiently await any new releases...
--Ed
|
It doesn't auto-flag spammers, it just compares them to what's already in the database. In order to add more information to the SFS database it must be when you mark them as a confirmed spammer. But right now it just checks to see if something is listed in the DB then if so marks them as failed, it doesn't submit any more information to SFS.
Perhaps its something the devs would consider.