From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org, Jeff Johnston <jjohnstn@redhat.com>
Subject: Re: Bugzilla spam
Date: Tue, 17 Apr 2007 04:26:00 -0000 [thread overview]
Message-ID: <20070417042612.GA18080@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4623F021.9040000@redhat.com>
On Mon, Apr 16, 2007 at 05:52:33PM -0400, Jeff Johnston wrote:
>I have recently been getting bugs opened against newlib which are spam.
> The bugs have nonsense in them with html attachments which redirect to
>porn pages, etc...
>
>Any plans in place to stop this or make it more difficult?
>
>Bug numbers include:
>
>4355
>4363
>4382
>
>All 3 bugs are from different e-mail addresses though 2 are randomized
>names from mailinator.com.
We could, at least, block their IP address if we have logged it.
cgf
next prev parent reply other threads:[~2007-04-17 4:26 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 [this message]
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
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=20070417042612.GA18080@ednor.casa.cgf.cx \
--to=me@cgf.cx \
--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).