Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!wp3b01!wjt
From: wjt@wp3b01.UUCP (Bill Taggart)
Newsgroups: news.admin,news.sysadmin,news.software.b
Subject: Re: Help- expire problem
Message-ID: <439@wp3b01.UUCP>
Date: Tue, 20-Oct-87 07:16:21 EDT
Article-I.D.: wp3b01.439
Posted: Tue Oct 20 07:16:21 1987
Date-Received: Wed, 21-Oct-87 23:43:25 EDT
References: <170@bnl.ARPA> <37f435e1.d130@starbarlounge.cc.umich.edu>
Reply-To: wjt@wp3b01.UUCP (Bill Taggart)
Distribution: na
Organization: AT&T Communications
Lines: 20
Summary: Not A Problem - It Is Normal Behavior
Xref: mnetor news.admin:1207 news.sysadmin:417 news.software.b:888

In article <37f435e1.d130@starbarlounge.cc.umich.edu> hyc@starbarlounge.cc.umich.edu (Howard Chu) writes:
>In article <170@bnl.ARPA> abrams@bnl.UUCP (Karl L. Abrams) writes:
>%When an article is due to expire, it is removed from the spool, but its
>%entry in history is only partially removed.  For example, [omitted]
>%...
>
>That's not exactly the normal behavior, but that's documented... 

From scanning the defs.h code in the news2.11 source it is
normal behavior.  DFLTEXP sets 2 weeks as the default for
expiring articles from the spool directories and HISTEXP sets
4 weeks to remove them from the history files.  This ensures
that old articles don't keep reappearing on your machine.  You
have a choice of either changing the defaults in the defs.h and
recompiling or use the expire -e and -E options.

-- 

	Bill Taggart
	{uunet | ihnp4}!wp3b01!wjt