public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifixinc.com>
To: Christopher Faylor <me@cgf.cx>
Cc: overseers@sourceware.org
Subject: Re: rms asking about badspammer.html
Date: Tue, 05 Apr 2005 19:49:00 -0000	[thread overview]
Message-ID: <1112730574.12942.9.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <20050401145623.GD25636@trixie.casa.cgf.cx>

On Fri, 2005-04-01 at 06:56, Christopher Faylor wrote:
> Check out /www/conf/spamblock.

Rms has asked that we have two files, instead of just the one
badspammer.html file.  One file would be used for known spambots.  And
the other would be for download accelerators.  If this is too
inconvenient, we could try to argue it with him.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com


      parent reply	other threads:[~2005-04-05 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  0:52 James E Wilson
2005-04-01 14:56 ` Christopher Faylor
2005-04-04 23:09   ` James E Wilson
2005-04-05 19:49   ` James E Wilson [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=1112730574.12942.9.camel@aretha.corp.specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=me@cgf.cx \
    --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).