Hi all,

Your project's Bugzilla database suffered some minor abuse earlier today
when a new user - ithanr...@gmail.com - started removing entries from CC
lists and replacing them with just themselves.

This is just a quick note to let you know that:

- The idiot concerned has had their account disabled.
- They have been removed from any CC list they added themselves to
- Any CC list they edited has been restored to its original value.

The corrective action has all been performed directly in the database
partly because it was a lot easier than going via the UI and partly so
your lists aren't spammed as each of the CC's was restored.

Mark


On 06/01/2019 15:23, Mark Thomas wrote:
> On 06/01/2019 13:28, Eric Covener wrote:
>> Some kind of weird abusive behavior this morning from
>> ithanr...@gmail.com hitting many bugs.
> 
> Seen it on Tomcat as well. I'm on it.
> 
> Mark
> 
> 
>>
>> ---------- Forwarded message ---------
>> From: <bugzi...@apache.org>
>> Date: Sun, Jan 6, 2019 at 8:24 AM
>> Subject: [Bug 53579] httpd looping writing on a pipe and unresponsive
>> (httpd <defunct>)
>> To: <b...@httpd.apache.org>
>>
>>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
>>
>> ithan <ithanr...@gmail.com> changed:
>>
>>            What    |Removed                     |Added
>> ----------------------------------------------------------------------------
>>                  CC|ar...@maven.pl,             |ithanr...@gmail.com
>>                    |loic.etienne@tech.swisssign |
>>                    |.com, mahud...@gmail.com,   |
>>                    |mark_a_ev...@dell.com,      |
>>                    |santhoshmukka...@gmail.com, |
>>                    |stix...@gmail.com,          |
>>                    |szg0...@freemail.hu         |
>>
>> --
>> You are receiving this mail because:
>> You are the assignee for the bug.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: bugs-h...@httpd.apache.org
>>
>>
>>
> 

Reply via email to