From owner-freebsd-current  Sat Sep 25 14:25:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id BD69D15328
	for <current@freebsd.org>; Sat, 25 Sep 1999 14:25:55 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11UzL5-000FDD-00; Sat, 25 Sep 1999 17:26:39 -0400
To: Jacques Vidrine <n@nectar.com>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	current@FreeBSD.ORG
From: "Gary Palmer" <gjp@in-addr.com>
Subject: Re: Filtering port 25 (was Re: On hub.freebsd.org refusing to talk to dialups) 
In-reply-to: Your message of "Fri, 24 Sep 1999 10:24:37 CDT."
             <19990924152438.F0C2BBE08@gw.nectar.com> 
Date: Sat, 25 Sep 1999 17:26:33 -0400
Message-ID: <58478.938294793@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jacques Vidrine wrote in message ID
<19990924152438.F0C2BBE08@gw.nectar.com>:
> > This prevents your customers from being something that could get you
> > on the RBL or the DUL MAP for bad behavior, it also inforces the use
> > of your smart host relay, as it/they is/are the only way to get a
> > tcp port 25 setup completed.
> 
> Evil!  How does the ISP know I'm not running some other protocol
> (which is none of its business) on port 25?

Because then you be failing to follow the relevant RFCs on port
assignments.

> How does it know that I don't have a policy reason for accessing
> some other mail server than its own?

It doesn't, but direct-inject and relay-rape spam is a major problem.
How do you propose that large ISPs combat abuse of their dialups to
create this problem?  Forcing the spam to go through their own SMTP
servers, where it can be logged, tracked, rate limited and noticed
much earlier is a BIG step in the right direction.  UU Net is doing
this for all of their resold dialups because of the major problems
they had.


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