From owner-freebsd-isp  Mon Sep 16 11:33:03 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA25721
          for isp-outgoing; Mon, 16 Sep 1996 11:33:03 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA25710
          for <isp@freebsd.org>; Mon, 16 Sep 1996 11:33:00 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA05985; Mon, 16 Sep 1996 13:30:50 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199609161830.NAA05985@brasil.moneng.mei.com>
Subject: Re: Denying expired users POP?
To: froden@bigblue.no
Date: Mon, 16 Sep 1996 13:30:50 -0500 (CDT)
Cc: davidn@blaze.net.au, isp@freebsd.org
In-Reply-To: <199609161553.RAA09216@login.bigblue.no> from "Frode Nordahl" at Sep 16, 96 05:02:51 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >-----BEGIN PGP SIGNED MESSAGE-----
> >
> >On Mon, 16 Sep 1996, Frode Nordahl wrote:
> >
> >>>yes, for expired user, we normally change their login shell, when compiling
> >>>qpopper, make that shell to deny mail.
> >>
> >>That is not a option.  I want it to use the expire date field in the passwd file.  Changing the shell is just extra 
> >>labour.
> >
> >Well, I certainly agree it isn't optimal. But writing a script to
> >change the passwd file (after looking at the expiry date)
> >wouldn't be particularly difficult.
> 
> If there is no other option, I guess I have to do that then :-(

Would it be smarter to create a patch to do the expiration thing, and 
then submit it someplace where folks are likely to find it useful?

I don't know who maintains qpopper, but if they're not willing to support
a vendor specific extension, it would still be nice to have it as a
"patch" that got bundled along with the FreeBSD port.

... JG