From owner-freebsd-questions Sat Dec 28 7:59:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FB5F37B401; Sat, 28 Dec 2002 07:59:22 -0800 (PST) Received: from hotmail.com (f152.law15.hotmail.com [64.4.23.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9FF643EA9; Sat, 28 Dec 2002 07:59:21 -0800 (PST) (envelope-from bill_moran2@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 28 Dec 2002 07:55:40 -0800 Received: from 66.132.12.15 by lw15fd.law15.hotmail.msn.com with HTTP; Sat, 28 Dec 2002 15:55:40 GMT X-Originating-IP: [66.132.12.15] From: "Bill Moran" To: htabak@quadtelecom.com, freebsd-questions@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: Bystander shot by a spam filter. Date: Sat, 28 Dec 2002 10:55:40 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 28 Dec 2002 15:55:40.0320 (UTC) FILETIME=[9202BA00:01C2AE89] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >From: Harry Tabak This is so crazy I had to respond. > My tiny x/29 block is sub-allocated from my DSL provider's x/23 block. > The DSL provider's block is a sub-allocation from Inflow.com's >66.45.0.0/17 block. Spambouncer doesn't like Inflow. While they have a >right to their opinions, they don't have a right to publicly tar me >because of my neighbors. Are you one of those people, that blames a car owner for not having an alarm system when his car gets stolen, instead of blaming the car thief? It's simple. Inflow is blocked for a reason. You can whine all you want, but spam filters never add default blocks unless an ISP has spammed, and refused to anything about it. Therefore, Inflow had to do at least 2 things: 1. Spam 2. Refuse to stop spamming after being contacted about it. I, personally, fully support their decision. There really needs to be some accountability on the Internet. Here's what you _should_ do: 1. Contact Inflow and raise a stink about how their poor policies are hurting you. 2. Find another provider. 3. Send a letter to the BBB complaining about Inflow's policies Even if you don't agree with me, I'll say that you're unlikely to have the FreeBSD people do anything? Have you emailed all the Linux distros as well and told them that there's an RPM out there that they should boycott? Are you now going to email every ISP on the planet and suggest that they boycott all FreeNIXes because they can use this anti-spam software? You're driving the wrong way on a "the other way" street, if you really want to accomplish anything. Put the pressure on the people who are doing wrong, not on the people trying to stop it. You shouldn't even have to contact the anti-spam developers, Inflow should contact them once they've improved their policy and demand that they be removed! _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 3 months FREE*. http://join.msn.com/?page=features/virus&xAPID=42&PS=47575&PI=7324&DI=7474&SU= http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_virusprotection_3mf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message