From: Konstantin Ryabitsev <mricon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Bugzilla spam
Date: Wed, 13 Jul 2016 14:37:56 -0400 [thread overview]
Message-ID: <20160713183756.GA3810@gmail.com> (raw)
In-Reply-To: <CAKgNAkiFnCHHERn5ECZ1xHhO6Y7jzsr7wrZB6o8wag2dceaaSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Wed, Jul 13, 2016 at 08:28:18PM +0200, Michael Kerrisk (man-pages) wrote:
> Hello Konstantin,
>
> The man-pages Bugzilla component (as well as other components on
> Bugzilla by the look of things) is receiving vast quantities of spam.
> What can be done about this? (Just marking the bugs private and
> closing isn't workable. There's just too many bugs coming in...).
Not much can be done. :( Bugzilla's default spam-fighting capabilities
are abysmal -- I can't even delete any accounts without installing
multiple extensions. I'm actively investigating what we can do to
improve the situation and will follow up shortly.
Regards,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-13 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 18:28 Bugzilla spam Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiFnCHHERn5ECZ1xHhO6Y7jzsr7wrZB6o8wag2dceaaSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-13 18:37 ` Konstantin Ryabitsev [this message]
[not found] ` <20160713183756.GA3810-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-13 18:48 ` Michael Kerrisk (man-pages)
2016-07-13 21:35 ` ellis
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=20160713183756.GA3810@gmail.com \
--to=mricon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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