all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Sven Joachim <svenjoac@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Spammers are now closing bugs
Date: Mon, 20 Apr 2009 07:41:19 +0800	[thread overview]
Message-ID: <49EBB69F.4050704@gnu.org> (raw)
In-Reply-To: <87ab6cphof.fsf@turtle.gmx.de>

Sven Joachim wrote:
> On 2009-04-19 21:20 +0200, Glenn Morris wrote:
>
>   
>> As far I am aware, this:
>>
>> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?msg=38;bug=1407
>>
>> is the first instance of spam closing a bug.
>>     
>
> Note that this will only happen to bugs that had been closed (and
> reopened) before, since this is necessary for the spammers to pick up
> the nnnn-done address.  In Debian, this issue had been discussed many
> times already, AFAICT without any solution.
>   

There is a very simple solution. Restrict bug closure and other 
administrative tasks to people on a list of emacs contributors and the 
original submitter. It is not a perfect solution, but it should deal 
with the problem of random spammers.




  reply	other threads:[~2009-04-19 23:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 19:20 Spammers are now closing bugs Glenn Morris
2009-04-19 19:28 ` Sven Joachim
2009-04-19 23:41   ` Jason Rumney [this message]
2009-04-20 10:48     ` Samuel Bronson
2009-04-20 14:27       ` Stefan Monnier
2009-04-20 18:18         ` Glenn Morris
2009-04-20 21:07           ` Stefan Monnier
2009-05-04 21:09             ` Glenn Morris
2009-05-05  3:55               ` Stephen J. Turnbull
2009-04-21  7:27           ` Alan Mackenzie
2009-04-21 17:16             ` Glenn Morris
2009-04-22  3:14               ` Stephen J. Turnbull
2009-04-22 17:07                 ` Eli Zaretskii
2009-04-20 18:14   ` Glenn Morris
2009-04-20 18:30     ` Sven Joachim
2009-04-20 18:40       ` Glenn Morris
2009-04-21  3:13         ` Stephen J. Turnbull
2009-04-21  3:31           ` Glenn Morris
2009-04-21  5:47             ` Miles Bader

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=49EBB69F.4050704@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=svenjoac@gmx.de \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.