public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "Jeff Johnston" <jjohnstn@redhat.com>, overseers@sourceware.org
Subject: Re: Bugzilla spam
Date: Tue, 17 Apr 2007 15:07:00 -0000	[thread overview]
Message-ID: <4aca3dc20704170807m26462233w331a9f2672633592@mail.gmail.com> (raw)
In-Reply-To: <4aca3dc20704170807s344f4155h5935939fe1f49588@mail.gmail.com>

On 4/17/07, Daniel Berlin <dberlin@dberlin.org> wrote:
> On 4/17/07, Frank Ch. Eigler <fche@redhat.com> wrote:
> > Hi -
> >
> > On Mon, Apr 16, 2007 at 11:09:19PM -0700, Daniel Berlin wrote:
> > > >[...] Any plans in place to stop this or make it more difficult?
> > >
> > > Like how? [...]
> >
> > For one thing, how does one *clean up* spam, that is, remove it from
> > the database?
> >
>
> perl /home/dberlin/userlookup.pl <emailaddressofspammer>
>
> mysql -u<mysql username> -p<mysql password> bugs (You can get the
> user/password from the userlookup.pl script)
> delete from longdescs where who=<id it printed out>

s/bugs/sourcesbugs/ for sources.redhat.com bugzilla.
>
> That will delete all comments from them.
> > - FChE
> >
>

  reply	other threads:[~2007-04-17 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  4:17 Jeff Johnston
2007-04-17  4:26 ` Christopher Faylor
2007-04-17  6:09 ` Daniel Berlin
2007-04-17 10:59   ` Frank Ch. Eigler
2007-04-17 15:07     ` Daniel Berlin
2007-04-17 15:07       ` Daniel Berlin [this message]
2007-04-17 16:11   ` Jeff Johnston
2012-03-13  9:48 bugzilla spam Jonathan Wakely
2012-03-13 10:44 ` Frank Ch. Eigler
2012-03-13 15:02   ` Paolo Carlini
2012-03-13 15:08     ` Frank Ch. Eigler
2012-03-14 10:38       ` Paolo Carlini

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=4aca3dc20704170807m26462233w331a9f2672633592@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=fche@redhat.com \
    --cc=jjohnstn@redhat.com \
    --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).