From: "Kelly Price" <strredwolf@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] aaaaaargh spam
Date: Thu, 15 Feb 2007 23:06:48 -0500 [thread overview]
Message-ID: <7ff566830702152006j362b610dmbbbc2c0ad650ee1b@mail.gmail.com> (raw)
In-Reply-To: <1171527870.28302.22.camel@violet>
On 2/15/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> to make this clear once and for all. Write to the Sourceforge guys and
> complain about the spam. I have no way to add spam filters to the
> mailing list.
>
> The bluez-users mailing list is now closed for subscribers, but for
> bluez-devel this is not an option. This mailing list is listed in the
> MAINTAINERS file of the Linux kernel and meant to be an open mailing
> list.
>
Can't you appoint a moderator for unsubscribed posts, if this is GNU
Mailman? I'm looking over the software's feature list, and it looks
like that's the best solution at this time if we can't close the list
to subscribers (even though subscribing is free and verified)
--
Kelly "STrRedWolf" Price
http://strredwolf.furrynet.com
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-02-16 4:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 23:00 [Bluez-devel] aaaaaargh spam Mike Hodson
2007-02-14 23:29 ` Thomas Kear
2007-02-15 8:24 ` Marcel Holtmann
2007-02-15 9:16 ` Mike Hodson
2007-02-15 22:34 ` Kinney Baughman
2007-02-16 3:51 ` Andrew Kohlsmith
2007-02-16 8:31 ` Marcel Holtmann
2007-02-16 4:06 ` Kelly Price [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=7ff566830702152006j362b610dmbbbc2c0ad650ee1b@mail.gmail.com \
--to=strredwolf@gmail.com \
--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