public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Gerald Pfeifer <gerald@pfeifer.com>, overseers@sourceware.org
Subject: Re: Remove or obfuscate spam in the *-bugs mailing lists?
Date: Wed, 10 Sep 2014 00:31:00 -0000	[thread overview]
Message-ID: <20140910003054.GA2936@ednor.casa.cgf.cx> (raw)
In-Reply-To: <alpine.LSU.2.11.1409092242580.2867@tuna.site>

On Tue, Sep 09, 2014 at 10:44:41PM +0200, Gerald Pfeifer wrote:
>On Tue, 9 Sep 2014, Christopher Faylor wrote:
>> But, it really bugs me that some evil dudes could try to subvert our
>> system so I'd like to eliminate any remaining benefit they could see
>> from sending spam here.
>
>Agreed. :-)
>
>> Thanks.  Which option do you prefer: Deleting or keeping munged,
>> content-free copies around?  The only reason that I could see for the
>> latter is that existing url references to the archives would continue to
>> work.  But, it's difficult to see any valid reason for a reference to
>> bugzilla spam.
>
>Would other, non-spam mails change their URLs as well?  If that's
>the case, munging might be better.  Otherwise I'd be in favor of
>simply yanking the crap.  Which seems to be your preference as well.

No, the mail would just disappear from the archive, leaving everything
else intact.  One other benefit with deletion is that since I'll be
using the mail archiver to delete it I won't have to worry about locking
the archives while I'm doing this.  That happens automatically.

So, it looks like I will be going with deletion.

If this seems to be reliable, I'll add a cron job to delete spam from
the archives automatically from now on.

cgf

      reply	other threads:[~2014-09-10  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 16:28 Christopher Faylor
2014-09-09 17:21 ` Gerald Pfeifer
2014-09-09 18:53   ` Christopher Faylor
2014-09-09 19:06     ` Jeff Law
2014-09-09 20:44     ` Gerald Pfeifer
2014-09-10  0:31       ` Christopher Faylor [this message]

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=20140910003054.GA2936@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gerald@pfeifer.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).