From owner-freebsd-security Wed Mar 14 6:27:57 2001 Delivered-To: freebsd-security@freebsd.org Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by hub.freebsd.org (Postfix) with ESMTP id 7EB7F37B718 for ; Wed, 14 Mar 2001 06:27:55 -0800 (PST) (envelope-from rjh@mohawk.net) Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by mohegan.mohawk.net (8.9.3/8.9.3) with ESMTP id JAA08446; Wed, 14 Mar 2001 09:42:54 -0500 (EST) (envelope-from rjh@mohawk.net) Date: Wed, 14 Mar 2001 09:42:54 -0500 (EST) From: Ralph Huntington To: "Bruce M. Walker" Cc: Jim Durham , freebsd-security@FreeBSD.ORG Subject: Re: Sophos and Virus return mail In-Reply-To: <200103141333.f2EDX0J19096@fusion.borderware.com> 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 > > > (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=- > > 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. Okay, so you meant blocking the 'escape' of packets bound for port 25 on any machine *other*than* the approved smtp host, which, of course, does not relay, correct? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message