From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 05 Feb 2007 04:07:57 -0800 (PST) Received: from mx1.suse.de (mail.suse.de [195.135.220.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id l15C7o3c023322 for ; Mon, 5 Feb 2007 04:07:52 -0800 From: Andi Kleen Subject: Re: Spam on list? Date: Mon, 5 Feb 2007 13:06:30 +0100 References: <68c491a60702050352t278e8381l72795ed9ea880029@mail.gmail.com> In-Reply-To: <68c491a60702050352t278e8381l72795ed9ea880029@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200702051306.34279.ak@suse.de> Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Martin =?iso-8859-1?q?Schr=F6der?= Cc: Eric Sandeen , Justin Piszcz , xfs@oss.sgi.com On Monday 05 February 2007 12:52, Martin Schröder wrote: > 05 Feb 2007 11:32:25 +0100, Andi Kleen : > > 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. -Andi