From owner-freebsd-security Wed Oct 29 08:02:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA24006 for security-outgoing; Wed, 29 Oct 1997 08:02:13 -0800 (PST) (envelope-from owner-freebsd-security) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA23994 for ; Wed, 29 Oct 1997 08:02:04 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id MAA06237 for ; Wed, 29 Oct 1997 12:06:53 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Wed, 29 Oct 1997 12:06:53 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: freebsd-security@FreeBSD.ORG Subject: Re: selective pop3 In-Reply-To: <19971029130053.20797@deepo.prosa.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk it wouldn't seem that hard to use the DB package to implement ACL (access control lists) with the pop3 server. On Wed, 29 Oct 1997, Philippe Regnauld wrote: > Piotr Szymanek writes: > > Is it possible to grant access to the pop3 server to some users and > > reject for the rest? > > > > If yes, then is it possible to restrict pop3 access based on clients > > address? > > Tcp wrappers. But you can only do IP level decisions, not user-level. > Or hack the pop3 server sources. > > -- > -- Phil > > -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- > -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- >