From owner-freebsd-isp  Sat Jan 10 20:47:25 1998
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA12281
          for isp-outgoing; Sat, 10 Jan 1998 20:47:25 -0800 (PST)
          (envelope-from owner-freebsd-isp)
Received: from eharden.com (eharden.com [207.193.60.129])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12263
          for <freebsd-isp@freebsd.org>; Sat, 10 Jan 1998 20:47:15 -0800 (PST)
          (envelope-from bad@uhf.wireless.net)
Received: from uhf.wireless.net (pp1.eharden.com [207.193.60.147])
	by eharden.com (8.8.7/8.8.5) with ESMTP id WAA12991;
	Sat, 10 Jan 1998 22:49:37 -0600 (CST)
Received: from localhost (bad@localhost)
	by uhf.wireless.net (8.8.8/8.8.7) with SMTP id WAA02260;
	Sat, 10 Jan 1998 22:54:55 -0600 (CST)
Date: Sat, 10 Jan 1998 22:54:55 -0600 (CST)
From: Bernie Doehner <bad@uhf.wireless.net>
To: Alan Batie <batie@agora.rdrop.com>
cc: Norman C Rice <nrice@emu.sourcee.com>, David Hawkins <dhawk@river.org>,
        freebsd-isp@freebsd.org
Subject: Re: How to lock out a nonpaying user?
In-Reply-To: <19980110103848.00312@agora.rdrop.com>
Message-ID: <Pine.BSF.3.96.980110225359.2239B-101000@uhf.wireless.net>
MIME-Version: 1.0
Content-Type: MULTIPART/SIGNED; PROTOCOL="application/pgp-signature"; MICALG=pgp-md5; BOUNDARY=Agd0e35j3NYeGe4z
Content-ID: <Pine.BSF.3.96.980110225359.2239C@uhf.wireless.net>
Sender: owner-freebsd-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--Agd0e35j3NYeGe4z
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-ID: <Pine.BSF.3.96.980110225359.2239D@uhf.wireless.net>

> All these complicated solutions when there's one already built into the
> password file: the expiration date.  I set up user's accounts so they
> expire at a certain time, and when they send more money, I adjust the
> expiration accordingly.  That way the system automatically handles it,
> and all I have to is the odd "oh please the check's in the mail and I
> really need my email" extensions at the beginning of the month.  I keep
> the paid-for expiration date in a separate file with scripts to munge
> things in batches for payment processing.
> 

I was going to say the same thing, however I tested it and for some stupid
reason you can still ssh into an expired account.. Haven't looked into it
yet.

Bernie

--Agd0e35j3NYeGe4z
Content-Type: APPLICATION/PGP-SIGNATURE
Content-ID: <Pine.BSF.3.96.980110225359.2239E@uhf.wireless.net>
Content-Description: 

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNLfAOIv4wNua7QglAQF8dgP/QWZfAtNHe0m9QFbcmkKzJes30oSU3TqO
4zqEkUIU8xDwB+haCF8fccqBjiO/QcvCh2xZi1AbVhVVO9vW8iSMvL/sjbTriBhx
/FIFxpInVri9rfIYglU9cTQyMT8eF5r8z6FxmKTpI9YtvVacBi5PP4AXisQmAEFh
dPwmG1NMxEU=
=ilH1
-----END PGP SIGNATURE-----

--Agd0e35j3NYeGe4z--