Closed Bug 410040 Opened 18 years ago Closed 17 years ago

Deal with annoying *6666@gmail.com user

Categories

(bugzilla.mozilla.org :: General, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: reed, Assigned: justdave)

References

()

Details

So, this guy is getting on everybody's nerves. Please figure out what to do about this guy for good, as he's really disrupting to triagers. Thanks! Accounts I've seen so far: * bank6666@gmail.com * berk6666@gmail.com * bom6666@gmail.com * castel6666@gmail.com * ford6666@gmail.com * htt6666@gmail.com * hyh6666@gmail.com * ralf6666@gmail.com * sat6666@gmail.com
So far, the above accounts have filed a combined total of 42 invalid/duplicate bugs.
So I'm having a hell of a time getting any way to block this guy because of it being in the cluster. On recluse I'd just iptables firewall the guy, or drop a deny from in the .htaccess file. But since we're behind a proxy that doesn't work. I tried adding this to the vhost config: RewriteCond %{HTTP_X_FORWARDED_FOR} ^166\.87\.255\. RewriteCond %{REQUEST_URI} !=/nuisancebugs2.html RewriteRule ^.* /nuisancebugs2.html [R=302,L] But it doesn't seem to be working (yes, verified the config actually got pushed, and apache had been restarted). The guy is on a dialup connection, always get an address from the same class C every time he dials in. I hate to block his whole ISP though.
I just pushed some perl code to Bugzilla's page init function to look for and attempt this redirect from there.
Netblock 166.87.0.0 - 166.87.255.255 is owned by the Saudi Arabian Oil Company (aramcoservices.com), and 166.87.255.* seems to be in Dhahran (Saudi Arabia). That seems to me a bored IT guy, not a customer from an ISP.
The Perl code I stuck in is successfully blocking the guy, he's hit it a few times now, and even emailed bugzilla-admin pointing out that he had been banned, to which I replied that he needed to explain what he was doing before I would unban him, and haven't heard back since. The Perl code is a major hack though, I don't want to have to be doing this for every IP we ever end up needing to block... oremj: any ideas why my rewrites didn't work in the cluster?
That rewrite looks correct to me. Did you test with your own ip?
No, but I watched the logs while the perp connected and didn't get redirected.
I added in the URL field the query which lets you view all bugs he reported, just in case.
justdave's trick on bmo worked... haven't seen this user in a while.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.