From: Florian Schmidt <mista.tapas@gmx.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
Carsten Koch <Carsten.Koch@icem.com>,
alsa-devel@lists.sourceforge.net
Subject: Re: Spam on Alsa-devel.
Date: Fri, 1 Oct 2004 18:12:28 +0200 [thread overview]
Message-ID: <20041001181228.7c9e28a6@mango.fruits.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0410011035300.2073@pnote.perex-int.cz>
On Fri, 1 Oct 2004 10:37:04 +0200 (CEST)
Jaroslav Kysela <perex@suse.cz> wrote:
> On Fri, 1 Oct 2004, James Courtier-Dutton wrote:
>
> > So, any post by a non-member will have to be authorised, the the
> > authorisation will be quiet.
> > In this way, you can filter out all SPAM manually, so that it does
> > not get posted to the list.
> > If mail is from the kernel mailing list, accept it, if it is from a
> > non-member, manually reject it, saying only members can submit
> > messages.
>
> I don't have a power to filter messages every day.. Any volunteer?
couldn't this be automated? every message having lkml somewhere in its
headers comes through? everything else from non members not.
flo
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-01 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 17:08 Re [1]: Wendell Jack
2004-09-30 17:43 ` Spam on Alsa-devel Carsten Koch
2004-09-30 18:25 ` Lee Revell
2004-09-30 21:11 ` Lee Revell
2004-10-01 6:01 ` Jaroslav Kysela
2004-10-01 8:32 ` James Courtier-Dutton
2004-10-01 8:37 ` Jaroslav Kysela
2004-10-01 16:12 ` Florian Schmidt [this message]
2004-10-01 17:19 ` Lee Revell
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=20041001181228.7c9e28a6@mango.fruits.de \
--to=mista.tapas@gmx.net \
--cc=Carsten.Koch@icem.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).