From owner-freebsd-questions Sat Jun 8 16:14:11 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA04367 for questions-outgoing; Sat, 8 Jun 1996 16:14:11 -0700 (PDT) Received: from info.infosite.com (root@info1.infosite.com [165.90.185.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA04342 for ; Sat, 8 Jun 1996 16:14:07 -0700 (PDT) Received: (from cslye@localhost) by info.infosite.com (8.6.12/beast-1.0) id UAA00286; Fri, 7 Jun 1996 20:48:58 -0700 From: Cameron Slye Message-Id: <199606080348.UAA00286@info.infosite.com> Subject: Re: Blocking access to Popper from outside To: compland@ism.com.br (Helio Coelho Jr. - CompuLand Informatica) Date: Fri, 7 Jun 1996 20:48:58 -0700 (PDT) Cc: questions@freebsd.org In-Reply-To: <199606082025.RAA22985@unix1.ism.com.br> from "Helio Coelho Jr. - CompuLand Informatica" at Jun 8, 96 05:25:30 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi: > > Is there a way to block people checking their mail in POPPER from outside > the local network ? Let me explain better: I have some dial in users that > are checking their mail remotely, from another network, through the WAN > port. I checked the POPPER man page but no luck. This can be done by > ip-filtering ? I can't figure how. Any help would be greatly appreciated ! TCP wrappers on the port would be the best bet... They are in the ports collection, I would recomend compiling it with the extended cheching option, this allowing you to have a hosts.allow file that you can define what can and cant do what on what port...