From owner-freebsd-ports@FreeBSD.ORG Sat Oct 21 01:07:54 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF6AE16A40F for ; Sat, 21 Oct 2006 01:07:54 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B7DD43D83 for ; Sat, 21 Oct 2006 01:07:46 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from db2.internal (db2.internal [10.202.2.12]) by frontend1.messagingengine.com (Postfix) with ESMTP id 4C0E3DB6DC5 for ; Fri, 20 Oct 2006 21:07:43 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by db2.internal (MEProxy); Fri, 20 Oct 2006 21:07:46 -0400 X-Sasl-enc: 3F0cOEC6x2+syDjG8rnlMhBQ5FjscI08p/9pu/adm+iW 1161392865 Received: from gumby.localdomain (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id BC6AE64E5 for ; Fri, 20 Oct 2006 21:07:45 -0400 (EDT) From: RW To: freebsd-ports@freebsd.org Date: Sat, 21 Oct 2006 02:07:36 +0100 User-Agent: KMail/1.9.4 References: <20061020214004.BFXX23386.ibm61aec.bellsouth.net@mail.bellsouth.net> <4539661C.1040003@joeholden.co.uk> In-Reply-To: <4539661C.1040003@joeholden.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610210207.38367.list-freebsd-2004@morbius.sent.com> Subject: Re: Please do not use spamcop to block email X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2006 01:07:54 -0000 On Saturday 21 October 2006 01:13, Joe Holden wrote: > Bo Briggs wrote: > > I received this, and > > > > Reason: Service unavailable; Client host [205.152.59.64] blocked using > > bl.spamcop.net; Blocked - see > > http://www.spamcop.net/bl.shtml?205.152.59.64 > > > > this is the bellsouth.net mail server. > > > > I respect the rdnsbl's, but please use spamcop as a filter, use > > cbl.abuseat.org if you want accurate results. Anyone can place an IP on a > > blacklist with a couple of reports to spamcop, and as I remember, it > > takes 24 hours before the block is in place. > > > > I've run a few mail servers before, and I do use the rdnsbl's, but > > spamcop is only used as a filter. > > > > Please reconsider using this as an absolute block. > > Valid points, however you should be asking your isp why they're on there > in the first place. I know its not as simple as that as I run several > mail clusters myself, but its not the responsibility of mailing lists to > ensure mail isn't blocked from what is listed in the rbl's. Well, should they be blocking with a list that's intended for scoring purposes? > Alternative > is to use your own mailserver, and not a widely abused isp mailserver. He can't really win. The normal advice these days is to relay though a smarthost to avoid dynamic address blocklists, which are considerably less aggressive than spamcop.