Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263772AbUDVBa0 (ORCPT ); Wed, 21 Apr 2004 21:30:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263777AbUDVBa0 (ORCPT ); Wed, 21 Apr 2004 21:30:26 -0400 Received: from mx1.redhat.com ([66.187.233.31]:7656 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S263772AbUDVBaW (ORCPT ); Wed, 21 Apr 2004 21:30:22 -0400 Date: Wed, 21 Apr 2004 21:30:12 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Miles Bader cc: Matti Aarnio , Jan De Luyck , , Subject: Re: vger.kernel.org is listed by spamcop In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1223 Lines: 28 On 22 Apr 2004, Miles Bader wrote: > Rik van Riel writes: > > I'm certain than vger got listed on spamcop due to linux-kernel > > subscribers reporting to spamcop some of the spam that leaked onto > > lkml, through Matti's strict filters. > > Does that mean that spamcop does no verification of user reports? Indeed. > I was under the impression that it's fairly easy to automatically check > whether a particular host is an open-relay or not, so it would seem kind > of irresponsible for spamcop not to do this if some people are relying > on their lists to do blocking (even if there's a disclaimer saying not > to do that, clearly people are ignorant or dumb, so why not play it safe?). Spamcop isn't doing any vulnerability checks I'm aware of. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/