Report each one as you find them using the triangle exclamation point. Might seem redundant, but it is possible for new spam to be posted before a block is completed.Is it sufficient to report one of the posts by a spammer, or do they all need to be tagged?
I'm thinking of these repeated multiple posts by the electronics jerks.
; <<>> DiG 9.3.2 <<>> @localhost direct-saleslimited.com NS ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17559 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;direct-saleslimited.com. IN NS ;; ANSWER SECTION: direct-saleslimited.com. 2364 IN NS dns142.c.register.com. direct-saleslimited.com. 2364 IN NS dns198.b.register.com. direct-saleslimited.com. 2364 IN NS dns082.d.register.com. direct-saleslimited.com. 2364 IN NS dns137.a.register.com. ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Jan 29 15:41:17 2013 ;; MSG SIZE rcvd: 142
The IP of 126.96.36.199 goes to Weebly.com; <<>> DiG 9.3.2 <<>> @localhost direct-saleslimited.com A ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22448 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;direct-saleslimited.com. IN A ;; ANSWER SECTION: direct-saleslimited.com. 2284 IN A 188.8.131.52 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Jan 29 15:42:04 2013 ;; MSG SIZE rcvd: 57
See posts #1 & 2... Grapeshot says it'd be a good idea to report each one, & whoever the first person to do it is, they should simply say that it's been reported so there aren't a flood of reports for the admins to deal with.pfries said:I report them but do not reply to the thread.
I generally only report one of the posts although sometimes there are a few.
Should one report all of the threads?
Should we reply to the post?
Almost all of the spam I have seen is coming from one company.
The admins just need to report them and they should be taken down.
Their registrar is register.com and I think their host is weebly.com.
This assumes that this isn't being done by a competitor of theirs to cause them flack.
The IP of 184.108.40.206 goes to Weebly.com
I should add that they are known to spam from IP's 220.127.116.11 and 18.104.22.168.
If you search the company name you will see forum after forum spammed. Since I am not an admin on this site I can not verify the spam truly originates from them and not an evil competitor.
Is there anyway to block any post with "direct-saleslimited.com" in it?The IPs we have seen over the last month cover the globe from Canada to LA to Singapore to Anonymous proxies.
I use this on another vbulletin forum and it does a good job at blocking the spammers from registering:The IPs we have seen over the last month cover the globe from Canada to LA to Singapore to Anonymous proxies.
HTHHow it Works
This data responsible for blocking user registrations comes from the stopforumspam.com (SFS) spammer database. After the user who is trying to register passes the built-in vBulletin registration checks which you have configured in your vBulletin settings, SOM then checks the SFS database to see if the IP, username, or email address that the user is trying to register with has been recently tagged as a known spam source on other forums around the Internet. Also can be configured to check the Akismet service for known comment spam.