From owner-freebsd-security Mon Jul 28 22:51:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12445 for security-outgoing; Mon, 28 Jul 1997 22:51:06 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12440 for ; Mon, 28 Jul 1997 22:51:03 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id BAA24219; Tue, 29 Jul 1997 01:50:59 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id BAA05362; Tue, 29 Jul 1997 01:50:59 -0400 (EDT) To: Vincent Poy cc: John Dowdal , security@FreeBSD.ORG, JbHunt , "[Mario1-]" From: "Gary Palmer" Subject: Re: security hole in FreeBSD In-reply-to: Your message of "Mon, 28 Jul 1997 22:44:23 PDT." Date: Tue, 29 Jul 1997 01:50:59 -0400 Message-ID: <5360.870155459@orion.webspan.net> Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Vincent Poy wrote in message ID : > I wasn't talking about erols but with some isp's for things such > as relaying spam mail. You can take legal action against people who's machines were exploited to relay spam mail? Wow! I think perhaps you have to understand that if they were used as a relay for spam mail, they are going to get *FLOODED* with mail (I know from experience). Theres not a thing you can do (well, I stayed up all night once and fitted anti-relay rules to sendmail, but in the past they weren't available). Most people will just delete or refile the complaints, since they can't really do anything about the user originated them. Complaining to relays rarely does any good. Either they can't be bothered to fix it, or don't know how. Thats when cisco access list rules to block their mail hosts come in handy. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info