From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116125 invoked by alias); 16 Aug 2016 14:41:29 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 116112 invoked by uid 89); 16 Aug 2016 14:41:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.3.2 spammy=permanently, evil X-HELO: gcc.gnu.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Aug 2016 14:41:18 +0000 From: "LpSolit at netscape dot net" To: overseers@gcc.gnu.org Subject: [Bug web/72856] Trottle bug creation for newly created accounts (to limit spam) Date: Tue, 16 Aug 2016 14:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: LpSolit at netscape dot net X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: LpSolit at netscape dot net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2016-q3/txt/msg00053.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D72856 --- Comment #10 from Fr=C3=A9d=C3=A9ric Buclin --- (In reply to Frank Ch. Eigler from comment #6) > Per-account rate limits seem so easy to overcome, with spammers already > creating numerous verified junk accounts with ease. I banned several ranges of IP addresses, and also permanently banned some domain names. Logs show that all evil attempts made today have been successfully blocked (for how long?). > I would suggest focusing on spam-prevention content analysis (spamassassin > style), and post-spam cleanup (blacklisting, history editing, bug hiding?) > efforts. Content analysis has been (partially) implemented today. If the bug report = is considered to be spam, the bug report is automatically rejected and the user account automatically disabled. --=20 You are receiving this mail because: You are on the CC list for the bug.