From owner-freebsd-security  Wed Mar 14  5:33:14 2001
Delivered-To: freebsd-security@freebsd.org
Received: from mgateway.borderware.com (mgateway.borderware.com [207.236.65.231])
	by hub.freebsd.org (Postfix) with ESMTP id 83D6537B719
	for <freebsd-security@FreeBSD.ORG>; Wed, 14 Mar 2001 05:33:11 -0800 (PST)
	(envelope-from bmw@borderware.com)
From: "Bruce M. Walker" <bmw@borderware.com>
Message-Id: <200103141333.f2EDX0J19096@fusion.borderware.com>
Subject: Re: Sophos and Virus return mail
In-Reply-To: <Pine.BSF.4.21.0103140841480.4793-100000@mohegan.mohawk.net> from
 Ralph Huntington at "Mar 14, 2001 08:42:23 am"
To: Ralph Huntington <rjh@mohawk.net>
Date: Wed, 14 Mar 2001 08:33:00 -0500 (EST)
Cc: "Bruce M. Walker" <bmw@borderware.com>,
	Jim Durham <durham@w2xo.pgh.pa.us>, freebsd-security@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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.)
> 
> If port 25 is blocked, then how is legitimate mail accepted?  -=r=-

[The instant I hit the "send" key, I knew I should have clarified! :-]

I meant, of course, blocking of port 25 to all destinations but the
"officially sanctioned mail server".  ISPs generally provide you
with a mail server IP which you are supposed to forward all mail
to.  Forcing all customers to go through that helps (a little) to
prevent spamming via open relays.  Yes, it annoys some, but clients
with dynamic addresses on DSL/cable modems usually don't care.

(Veering dangerously OT now...)

-bmw

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message