From owner-freebsd-isp Mon Apr 20 08:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14076 for freebsd-isp-outgoing; Mon, 20 Apr 1998 08:29:46 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from marlin.corp.gulf.net (calvin@marlin.corp.gulf.net [198.69.72.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13956 for ; Mon, 20 Apr 1998 15:28:49 GMT (envelope-from calvin@marlin.corp.gulf.net) Received: from localhost (calvin@localhost) by marlin.corp.gulf.net (8.8.8/8.8.5) with SMTP id KAA09327 for ; Mon, 20 Apr 1998 10:23:43 -0500 (CDT) Date: Mon, 20 Apr 1998 10:23:43 -0500 (CDT) From: Calvin Meloon To: isp@FreeBSD.ORG Subject: extra email accounts 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 Here's the scenario. Our isp offers 2 extra email accounts for each customer who subscribes with us. Lately, we've noticed that some have been dialing up with their second email account (I believe they are giving the name and password out to friends or what not). What I'm looking for is a way to prevent the extra accounts to be used for dialup and still allow the user to pop their mail the same way they can from their main account. I thought of using the radius user file and just add a bogus password, thus allowing them to retrieve mail, but not be able to dial in. This, however seems kind of awkward and tedious. Anyone ideas? _____ __ _ / ___/__ _/ / __(_)__ Gulf Coast Internet Calvin M. Meloon / /__/ _ `/ / |/ / / _ \ Pensacola, FL Unix Administrator \___/\_,_/_/|___/_/_//_/ (850)438-5700 writer of code ~~~~ calvin@gulf.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Proponent of FreeBSD and the right of everyone to use a real OS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message