From owner-freebsd-security Wed Mar 14 15:47:58 2001 Delivered-To: freebsd-security@freebsd.org Received: from daedalus.cs.brandeis.edu (daedalus.cs.brandeis.edu [129.64.3.179]) by hub.freebsd.org (Postfix) with ESMTP id 314E737B77B for ; Wed, 14 Mar 2001 15:47:51 -0800 (PST) (envelope-from meshko@daedalus.cs.brandeis.edu) Received: from localhost (meshko@localhost) by daedalus.cs.brandeis.edu (8.9.3/8.9.3) with ESMTP id SAA03451; Wed, 14 Mar 2001 18:47:45 -0500 Date: Wed, 14 Mar 2001 18:47:45 -0500 (EST) From: Mikhail Kruk To: Szilveszter Adam Cc: Subject: Re: Sophos and Virus return mail In-Reply-To: <20010314231442.F12391@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ralph Huntington wrote: > > > > (This is one case where blocking of port 25 by ISPs is a good thing.) > > Yes. And makes using eg send-pr(1) real fun(TM). Enjoying all the benefits > of such a setup right now. While we are at it, why not firewall off the > whole Net by just allowing a few things through proxies like www and ftp > just so that a few morons are safe? Anyways, who would use such esoteric > things as "cvsps" or "cvsup" and what are these etc. You can see where this > is leading. Unfortunately network administration only looks simple if you > are the one sitting at the admin console. Otherwise, it can quickly become > a set of annoying limitations that hinder you @work or @play. Cool. I > really feel like paying a lot for Internet access with these conditions. My DSL provider, Mindspring, blocks port 25 and I am quite happy about it. Of course send-pr doesn't work out of the box, but you can configure everything to work through their mail server. Blocking one port is very far from blocking all ports except 80, it's a bad analogy. This measure is directed at a very specific kind of activity (spamming) and does not affect vast majority of the users. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message