Getting back to spam killing forums, I was forced to pre-moderate all new member posts, simply because of machine gun Xrumer spambots dumping image embedded porn threads and the same with the Viagra morons dumping long threads with ad images embedded.
Now these Black Hat Spam-E-O scum bags are simply content with dumping links in forum user profile slots by the thousands with Xrumer spam scripts, so now I have to find a way to take all live link fields out of forum user profile forms for new members.
Some of these low life's have thousands of accounts on each forum they spam, so they could have the same amount of outgoing links just in forum user profile homepage link slots.
Forum software must be more versatile allowing administrators to remove (or add) live link slots for various user groups in the future.
OK, please explain how this is done in detail for folks that do not code.
- Add regular expressions to profile fields to prevent links from being added.
^[A-Z0-9 ]+$
I still don't get it to be honest, if a new member can enter a homepage link why would a bot not be able to in the forum user profile homepage slot ??
I use the regex in profile fields like occupation, interests etc.
We had the same issues a while ago.
Currently we are using a mixture of:
- User Agent based blocking
- Referrer blocking
- Header based blocking
I still don't get it to be honest, if a new member can enter a homepage link why would a bot not be able to in the forum user profile homepage slot ??
I am talking about the homepage link slot and how to eliminate that for new members (that user group) specifically.
I just wonder why that permission does not exist in the user group permissions (the one to eliminate homepage link) like you can with signatures.
That's what I liked about IPB3 compared to vBulletin. You can set-up the first members user-group to NOT do things like add a signature and homepage link e.t.c. Not until they reach so many posts made on the open forums, or reach the next members group.
Hi,
On our Website we currently block:
UserAgents:
Java/1.6.0_22
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Babya Discoverer 8.0:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Crazy Browser 1.0.5)
Plus chinas Baidu Spider, as the UserAgent block is quicker than the Country block due to the database size
Referrers:
Referrer are pretty unique to each software product/website, as Spammers use different search strings for different target systems
Headers:
We integrated BadBehavior as a module into our AntiSpam software and let it do all the header filtering, while our Software does the IP, Charset and RFI filtering
Techniques are likely to change over time, and hence we may have to block more UserAgents in the future.
But for now, our configuration gives us a good nights sleep
We use essential cookies to make this site work, and optional cookies to enhance your experience.