From owner-freebsd-isp Wed Sep 18 10:12:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26427 for isp-outgoing; Wed, 18 Sep 1996 10:12:19 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26395 for ; Wed, 18 Sep 1996 10:12:15 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA25046; Wed, 18 Sep 1996 19:08:50 +0200 Message-Id: <199609181708.TAA25046@login.bigblue.no> From: "Frode Nordahl" To: "Joe Greco" Cc: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 18:18:19 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996 13:30:50 -0500 (CDT), Joe Greco wrote: >> >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. I agree! Should be a part of a port in the ports collection or something... I'll try to contact the maintainers of qpopper and see if they are interested in implementing such a feature. If not I would be more than glad if someone would like to patch it for us... I'm not a C programmer, so It's not likelly that I can do such a thing... --------------------------------- Frode Nordahl