public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan <alan@ufies.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Spam filters
Date: Fri, 27 Sep 2002 09:17:04 -0700	[thread overview]
Message-ID: <20020927161704.GA641@ufies.org> (raw)
In-Reply-To: <20020927150350.GK19495@kruhft.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

On Fri, Sep 27, 2002 at 08:03:50AM -0700, Burton Samograd wrote:
> On Fri, Sep 27, 2002 at 02:28:08PM +0200, Henrik Treadup wrote:
> > Spam is (I assume) a problem not only for the gentoo-dev mailing list but 
> > also for all other gentoo lists. Closing gentoo-dev doesn't solve the 
> > problem. The other lists will still get spam.
> > Should the other lists also be closed? (Closing gentoo-newbies is probably 
> > a bad idea.) The solution IMHO is a filter on the gentoo mailserver. 
> > 
> 
> How is making the list subscriber only closing it?  I'm on about 20
> other mailing lists, all subscribe only and I get no spam on them.
> This problem has been solved long ago...there is no need to waste
> server processor cycles for spam filtering on lists.  If people are
> scared that there newbies 'won't be able to figure out' hot to
> subscribe, I'm on some music development lists where the people on
> there barely even know how to use the computer for anything else other
> than email and can still figure it out.
> 
> I'm pretty sure that anybody that uses email can figure out how to
> read a page, send an email and a send a reply when they get it.

I have to agree with this.  Someone mentioned the reason was
accessability to new users, but I'm in the same situation as Burton, on
a bunch of lists, all subscriber only, except for gimp-dev (which gets
spam as well, or did when I was still receiving mail to it).  My feeling
is that if a new users isn't smart enough to go to a web page and fill
in an email, then respond to a message, will the be able to post to the
list, and then find the list archives to search for any answers?  Of
course they could just asked to be cc'd on replies, but that is bad
netiquette, and we don't want to encourage that :) 

The other thing is that the only gentoo list I'm getting spam from is
gentoo-dev, so obviously someone got it on a spam list somewhere, and
why not close down the list with the problem (and the list less likely
to get newbies on it IMHO).  

Totally OT, I installed bogofilter this morning thanks to the
suggestions on the list, and it seems to be working fine so far.  Only
one piece of spam caught, but it's one for one so far :)  Kinda wierd
when you actually *want* spam (if only to catch it!)

Regards,

Alan


-- 
Alan "Arcterex" <alan@ufies.org>   -=][=-   http://arcterex.net
"I used to herd dairy cows. Now I herd lusers. Apart from the isolation, I
think I preferred the cows. They were better conversation, easier to milk, and
if they annoyed me enough, I could shoot them and eat them." -Rodger Donaldson

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-09-27 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 12:28 [gentoo-dev] Spam filters Henrik Treadup
2002-09-27 15:03 ` Burton Samograd
2002-09-27 16:17   ` Alan [this message]
2002-09-27 19:13     ` Fredrik Jagenheim
2002-09-28 13:15       ` [OT] spam hunting was " Alan
2002-09-28  3:54   ` Viktor Lakics
2002-09-28  9:25     ` [gentoo-dev] " Mark Gordon
2002-09-28 10:33       ` Alexander Gretencord

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=20020927161704.GA641@ufies.org \
    --to=alan@ufies.org \
    --cc=gentoo-dev@gentoo.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