Linux bluetooth development
 help / color / mirror / Atom feed
From: Stefan Behlert <behlert@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] spam controls
Date: Fri, 16 Feb 2007 20:30:00 +0100	[thread overview]
Message-ID: <20070216193000.GD28471@suse.de> (raw)
In-Reply-To: <5b9417770702161119k29faadd4p64bd042c7fc8c50a@mail.gmail.com>

Moin,

On Feb 16, 07 13:19:08 -0600, John H. wrote:
> Well, I think a lot of basic spam filters deal with things such as
> subject, and in this case, bluez is in the subject, so i don't want to
> prevent that.

I know no spam filter that judges only based on Subject. I think that would
be a very poor filter, indead.

Every spam filter worth its name parses the content, and weights it.

> I am confused why, like other lists, there can not be a requirement
> that you belong to a list to mail the list.

As the other Stefan explained to you:
        "Not if it is listed as contact in the MAINTAINERS file."

Also this statement might be questionable in it's absolut form, he has a
point there.

You _could_ use a spam filter, you know?
And besides that the best way would be to activate a spam filter in the
mailing list program. But I do not know if that is possible for that list

        ciao,
          Stefan


> =

> On 2/16/07, Stefan Behlert <behlert@suse.de> wrote:
> > Moin,
> >
> > On Feb 16, 07 11:26:24 -0600, John H. wrote:
> > > Considering there are at least several spams a day, I know for a fact
> > > that's not true.
> >
> > Why should it be "not true" if he has working spam-filters?
> > Looks like you don't have those, which is very surprising.
> > >
> > > On 2/16/07, Stefan Seyfried <seife@suse.de> wrote:
> > > > On Fri, Feb 16, 2007 at 10:25:10AM -0600, John H. wrote:
> > > > > Please, can't you just make it to where only members can post?
> > > >
> > > > No. Not if it is listed as contact in the MAINTAINERS file.
> > > > Discuss whatever you want, it won't help.
> > > >
> > > > And i have gotten much more useless mails from this "STOP ZE SP=C4M=
!"
> > > > thread than from spamers directly.
> >
> >
> > But looking in my spam folder I agree that there are several spam-mails
> > each day. A spam-filter for the list would not be a bad idea, true.
> > But until then I can live with my own spam-filters.
> >
> >         Stefan
> >
-- =

Stefan Behlert

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-02-16 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 19:19 [Bluez-devel] spam controls John H.
2007-02-16 19:30 ` Stefan Behlert [this message]
2007-02-16 21:04   ` Marcel Holtmann
2007-02-16 19:30 ` Stefan Seyfried
2007-02-16 19:35   ` John H.
2007-02-17  2:09   ` Kelly Price
2007-02-17 10:39     ` Marcel Holtmann
2007-02-17 17:21       ` Kelly Price

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=20070216193000.GD28471@suse.de \
    --to=behlert@suse.de \
    --cc=bluez-devel@lists.sourceforge.net \
    /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