From owner-freebsd-isp Tue Mar 9 13:46:57 1999 Delivered-To: freebsd-isp@freebsd.org Received: from host07.rwsystems.net (kasie.rwsystems.net [209.197.192.103]) by hub.freebsd.org (Postfix) with ESMTP id 8DC1A14D7F for ; Tue, 9 Mar 1999 13:46:53 -0800 (PST) (envelope-from jwyatt@RWSystems.net) Received: from kasie.rwsystems.net([209.197.192.103]) (1436 bytes) by host07.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Tue, 9 Mar 1999 15:28:29 -0600 (CST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-24) Date: Tue, 9 Mar 1999 15:28:24 -0600 (CST) From: James Wyatt To: "Nicholas J. Dear" Cc: freebsd-isp@FreeBSD.ORG Subject: Re: POP3 boxes. In-Reply-To: <199903091736.RAA26419@post.mail.areti.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of course there are other ways to do it, this is Unix, right? 8{) On Tue, 9 Mar 1999, Nicholas J. Dear wrote: > We currently do POP3 boxes by creating a user and setting their shell to > /bin/false and directing all mail to that account. > > Is there any other way to do it? If so, with what software, and would it require > much work to implement? If you are doing it this way, however, I would recommend using /bin/passwd as it lets users telnet to change their passwords. You also want to ensure you deny them FTP access if they have valid accounts and shells. Your options depend on your POP server; most allow for other authenticaion mechanisms like DBM files, radius, and such. You will also want to use something other than /etc/passwd entries if you want to support hundreds or thousands of POP users. Knowing this group, more useful advice should be forthcoming - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message