From: Nathan Scott <nscott@aconex.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Andi Kleen" <ak@suse.de>, "Martin Schröder" <martin@oneiros.de>,
"Justin Piszcz" <jpiszcz@lucidpixels.com>,
xfs@oss.sgi.com
Subject: Re: Spam on list?
Date: Tue, 06 Feb 2007 08:58:50 +1100 [thread overview]
Message-ID: <1170712730.18017.452.camel@edge> (raw)
In-Reply-To: <45C73CB9.5000402@sandeen.net>
On Mon, 2007-02-05 at 08:18 -0600, Eric Sandeen wrote:
> Andi Kleen wrote:
> > On Monday 05 February 2007 12:52, Martin Schröder wrote:
> >> 05 Feb 2007 11:32:25 +0100, Andi Kleen <ak@suse.de>:
> >>> Please don't do that. It means nothing can be cross posted
> >>> from l-k anymore, which would be pretty bad.
> >> Then set up a list admin who can approve such postings.
> >
> > That adds unacceptable latency. Also lists who spam senders
> > with bounce messages tend to be dropped quickly from cc lists.
> >
> > Also you couldn't list xfs@ as bug report address anymore because
> > bug report addresses must be available to everyone.
> >
> > In general it's a bad idea.
*nod*, it really cannot become a closed list.
>
> Well, I agree w/ those arguments too, Andi.
>
> I honestly don't know why oss seems to have so much more spam than, say,
> LKML. It is getting to a really bad level, and I sympathize with those
> whose inboxes are bombarded, too.
Another option would be to move the list to vger.kernel.org and have
it spam protected by whatever they're successfully using over there
already (or maybe ask Davem what they're using and replicate on oss?).
cheers.
--
Nathan
next prev parent reply other threads:[~2007-02-05 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 13:25 Spam on list? Justin Piszcz
2007-02-04 18:44 ` Eric Sandeen
2007-02-04 19:18 ` Emmanuel Florac
2007-02-04 21:46 ` Eric Sandeen
2007-02-05 10:32 ` Andi Kleen
2007-02-05 9:59 ` Jason White
2007-02-05 11:52 ` Martin Schröder
2007-02-05 12:06 ` Andi Kleen
2007-02-05 14:18 ` Eric Sandeen
2007-02-05 21:29 ` Sami Farin
2007-02-05 21:58 ` Nathan Scott [this message]
2007-02-05 23:47 ` Eric Sandeen
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=1170712730.18017.452.camel@edge \
--to=nscott@aconex.com \
--cc=ak@suse.de \
--cc=jpiszcz@lucidpixels.com \
--cc=martin@oneiros.de \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox