From: Joel Brobecker <brobecker@adacore.com>
To: overseers@sourceware.org
Cc: Pedro Alves <pedro@palves.net>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: getting spammed on bugzilla
Date: Thu, 11 Nov 2021 07:29:42 +0400 [thread overview]
Message-ID: <YYyOJhziKpa5jBgo@adacore.com> (raw)
Hello,
Our bugzilla instance is being used as a spamming platform.
Spammers do so by just posting answers to random PRs.
As a result of this:
- The PRs gets polluted with these annoying messages that
we cannot remove (just mark as spam, which is a game of
wack-a-mole and personally a waste of our precious time);
- People on the Cc: list get emails about them.
I wouldn't be exagerating if I said that 95% of emails I am
getting from bugzilla, at the moment, is spam.
I think the problem is that spammers can create their account
without any form of validation.
Is there something we could do about this?
Pedro tells us that:
> LLVM has solved this by disabling new user self-registration:
>
> https://bugs.llvm.org/enter_bug.cgi
>
> "New user self-registration is disabled due to spam. For an account please email
> bugs-admin@lists.llvm.org
> with your e-mail address and full name."
I'm happy to help with answering those legitimate account
creations, if that makes a differnce.
Any other ideas, perhaps?
Thank you!
--
Joel
next reply other threads:[~2021-11-11 3:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:29 Joel Brobecker [this message]
2021-11-11 3:47 ` Andrew Pinski
2021-11-12 4:40 ` Joel Brobecker
2021-11-12 8:55 ` Mark Wielaard
2021-11-12 13:26 ` Carlos O'Donell
2021-11-22 4:03 ` Joel Brobecker
2021-11-24 10:09 ` Mark Wielaard
2021-11-24 14:55 ` Frank Ch. Eigler
2021-11-24 23:40 ` Mark Wielaard
2021-11-25 0:19 ` Frank Ch. Eigler
2021-11-25 17:49 ` Joseph Myers
2021-11-25 17:54 ` Frank Ch. Eigler
2021-11-25 17:59 ` Joseph Myers
2021-11-28 17:01 ` Mark Wielaard
2021-11-28 17:35 ` Frank Ch. Eigler
2021-11-28 18:07 ` Mark Wielaard
2021-11-29 17:12 ` Joseph Myers
2021-12-17 2:50 ` Joel Brobecker
2021-12-17 17:19 ` Frank Ch. Eigler
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=YYyOJhziKpa5jBgo@adacore.com \
--to=brobecker@adacore.com \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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).