public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* Bugzilla Bug 605 fun fixed
@ 2003-08-05 2:51 Daniel Berlin
0 siblings, 0 replies; only message in thread
From: Daniel Berlin @ 2003-08-05 2:51 UTC (permalink / raw)
To: gcc-bugs; +Cc: gcc, overseers
For those who don't know, someone using a challenge response system
unknowingly (presumably, since he never got the emails, since they
never made it through!) caused 194 comments to be appended to a bug
over the course of the past 1 hour, because it decided to reply to a
gcc-bugs email.
It also caused 194 messages to gcc-bugs as a result of adding these
comments.
So I disabled his bugzilla account, and changed bugzilla_email_append
not to append comments from disabled users.
This is also serving as fair warning to anyone using these challenge
response systems:
Please either make sure they let through gcc-bugs mail, or aren't
stupid enough to respond to the sender of list mails.
I've copied overseers so you guys know this is taken care of.
You may want to hand-remove the 194 messages from the list archives so
they don't pollute it, if easily possible.
--Dan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-08-05 2:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-08-05 2:51 Bugzilla Bug 605 fun fixed Daniel Berlin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).