From: Manuel Naranjo <naranjo.manuel@gmail.com>
To: thomas.kear@gmail.com, BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] SPAM IN THE LIST
Date: Thu, 26 Oct 2006 23:20:18 -0300 [thread overview]
Message-ID: <45416CE2.2080804@gmail.com> (raw)
In-Reply-To: <200610271514.13687.thomas.kear@gmail.com>
Thomas Kear wrote:
> I've been getting it too. I've been attemptiong (in vain it seems) to train
> gmail's spam filter by reporting everything that hits my inbox, but it looks
> like I'm going to have to look for a more serious solution in KMail.
>
> The ideal solution would be for the list admins to close posting access to
> only people registered on the list, this seems to have stemmed the similar
> flood of nonsense that was plaguing the inkscape-devel mailing list.
>
All of us are getting a lot of Spam. This is because SourceForge don't
have very good Spam filters. I don't think that closing the mailing list
to only registered people can be an option, but we should find a way to
contribute with SourceForge to end with this, the same is happening in
another list that I'm suscribed Linux-Usb-(devel or user)
Cheers,
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-10-27 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 1:46 [Bluez-users] SPAM IN THE LIST Jaime Alberto Silva
2006-10-27 2:14 ` Thomas Kear
2006-10-27 2:20 ` Manuel Naranjo [this message]
2006-10-27 8:39 ` Jose Bernardo Silva
2006-10-27 11:09 ` James Blackwell
2006-10-27 22:00 ` Thomas Kear
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=45416CE2.2080804@gmail.com \
--to=naranjo.manuel@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=thomas.kear@gmail.com \
/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.