public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frédéric Buclin" <LpSolit@netscape.net>
To: GCC Mailing List <gcc@gcc.gnu.org>
Cc: overseers@sourceware.org
Subject: New anti-spam extension enabled on GCC Bugzilla
Date: Sun, 31 Aug 2014 22:50:00 -0000	[thread overview]
Message-ID: <5403A69F.4060003@netscape.net> (raw)

Hello,

I just enabled an extension on GCC Bugzilla which automatically disables
reporter's account if their bugs are marked as INVALID and are in the
'spam' component. So if you have enough privileges on GCC Bugzilla to
close a bug as INVALID and to move it in the 'spam' component (in the
'gcc' product), you can help disabling these user accounts. It doesn't
matter if the bug is closed as RESOLVED or CLOSED. What matters is the
INVALID resolution. Note that you won't see any notification that the
account has been disabled. That's expected. :)

I re-enabled user account creation a few minutes ago, and already 2 new
accounts have been created. Both are spammers. I have disabled them already.

Note that my extension only disables reporters. It doesn't disable
commenters who are also spammers (because we have no way to mark a
comment as spam yet. This feature will come with Bugzilla 5.0). For
them, admins will have to disable these accounts manually:

https://gcc.gnu.org/bugzilla/editusers.cgi

You type the email address of the user you want to find, then click on
it and type some text in the "Disable text" field. You can also click
the "Bugmail Disabled" checkbox to prevent the spammer from getting any
new bugmail. Do not forget to click the "Save Changes" once you are done.


Good luck!

Frédéric


PS: Do not hesitate to email me if there is something wrong with my
extension.

             reply	other threads:[~2014-08-31 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 22:50 Frédéric Buclin [this message]
2014-09-02  8:05 ` Richard Biener

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5403A69F.4060003@netscape.net \
    --to=lpsolit@netscape.net \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).