From: Kinney Baughman <baughmankr@appstate.edu>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] aaaaaargh spam
Date: Thu, 15 Feb 2007 17:34:05 -0500 [thread overview]
Message-ID: <45D4DFDD.7010306@appstate.edu> (raw)
In-Reply-To: <9da483cb0702150116i26044caieb542012c3471332@mail.gmail.com>
Mike Hodson wrote:
> On 2/15/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>> Hi Thomas,
>> 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.
>>
> And I did just that, submitted a "excessive spam" support ticket to
> their support system. We'll see if anything comes of it ...
>
> And, I'm still planning to re-test my spider with the newest build,
> but I've been busy :)
At the risk of promising more than I can deliver, the list runs on
Mailman. I run that on my server. I'll take a look at the code and see
if there's a way to trap on certain patterns in the spam posts that come
through. I've been deleting them but I'll start saving them and see
what kind of patterns can be discerned. Maybe we can catch at least
some of what comes through.
--
Kinney
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-02-15 22:34 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 [this message]
2007-02-16 3:51 ` Andrew Kohlsmith
2007-02-16 8:31 ` Marcel Holtmann
2007-02-16 4:06 ` 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=45D4DFDD.7010306@appstate.edu \
--to=baughmankr@appstate.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.