From owner-freebsd-chat@FreeBSD.ORG Sun Nov 19 23:14:36 2006 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 26B3416A500 for ; Sun, 19 Nov 2006 23:14:36 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BDA743D96 for ; Sun, 19 Nov 2006 23:14:17 +0000 (GMT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.13.8/8.13.8) with ESMTP id kAJNESht024946; Sun, 19 Nov 2006 16:14:28 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.13.8/8.13.8/Submit) with ESMTP id kAJNESPw024943; Sun, 19 Nov 2006 16:14:28 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 19 Nov 2006 16:14:28 -0700 (MST) From: Warren Block To: Stefan Bethke In-Reply-To: <41576AD6-3ADA-4DB4-8442-EA422BAC9E03@lassitu.de> Message-ID: <20061119155628.B24876@wonkity.com> References: <41576AD6-3ADA-4DB4-8442-EA422BAC9E03@lassitu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (wonkity.com [127.0.0.1]); Sun, 19 Nov 2006 16:14:28 -0700 (MST) Cc: freebsd-chat@freebsd.org Subject: Re: spamcop now completely broken? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 23:14:36 -0000 On Sun, 19 Nov 2006, Stefan Bethke wrote: > Is is just me, or has SpamCop become useless? Two weeks ago, they were > listing apache.org, now they're listing freebsd.org... Looks like they're blocking mx2, 69.147.83.53. That's the new address since Friday. It says "Spamcop users have reported system as a source of spam less than 10 times in the last week." I've heard that Spamcop has a pretty high false positive rate, higher than some other DNSBLs that have a reputation for it, but I haven't used the Spamcop DNSBL. Just looking this up and comparing a few other things, it doesn't look like much. The old addresses for mx1 and mx2 were in my access.db with "OK" codes for a long time, so now seems to be a good time to add the new addresses, 69.147.83.52 and .53. -Warren Block * Rapid City, South Dakota USA