From owner-freebsd-current Sun Sep 26 10:22:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BC7115190 for ; Sun, 26 Sep 1999 10:22:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA66881; Sun, 26 Sep 1999 10:22:28 -0700 (PDT) (envelope-from dillon) Date: Sun, 26 Sep 1999 10:22:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199909261722.KAA66881@apollo.backplane.com> To: "Gary Palmer" Cc: Brian Somers , current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups References: <63983.938365645@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Brian Somers wrote in message ID :<199909261052.LAA23749@keep.lan.Awfulhak.org>: :> I think it's up to the ISP what default policies they have, and I :> also think that this sort of policy is a good default... but only as :> long as the ISP allows exceptions. As a paying subscriber with a :> clean record I *must* be allowed to ask for a hole through your :> firewall. : :No, actually, there is absolutely nothing which says that you, as a :subscriber of good standing, *have* to be allowed to connect to :non-local port 25. I think it is perfectly reasonable that the ISP :require that you buy a static IP (with N months initially prepaid) or :something to get port 25 privs. ISP's have begun to do this sort of blocking because dialup spammers abuse their privilages so much that a single spammer can cause an ISP to get inundated with complaints, yet the ISP can do little about it other then kick the spammer off (which solves nothing, really, considering how cheap dialup accounts are). Frankly, I have to agree that no dynamic dialup user should be allowed to connect through to port 25 on anything but the ISPs own mail server. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message