Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!shadooby!accuvax.nwu.edu!tank!ncar!ames!lll-winken!uunet!mcvax!ukc!strath-cs!glasgow!icdoc!syma!andy
From: andy@syma.sussex.ac.uk (Andy Clews)
Newsgroups: news.sysadmin
Subject: Re: expire line abuse
Message-ID: <873@syma.sussex.ac.uk>
Date: 5 Apr 89 12:21:26 GMT
References: <7704@killer.Dallas.TX.US>
Organization: University of Sussex
Lines: 27

From article <7704@killer.Dallas.TX.US>, by root@killer.Dallas.TX.US (Admin):
> 
>      In investigating why articles were not being expired, I discovered the
> following - all by an individual who has set expire lines for length of times
> from two months to two years. 

[about 500 lines deleted]

set flame

Why was it necessary to include the contents of all those articles just to
illustrate the silly expiry dates? Surely a bit of editing would have left
us with just the "Expires:" lines instead of adding to net congestion.

unset flame

Why not set your "expire" to ignore explicit expiry dates? The -I option
does this. Unless maybe you have some articles which really need to be kept
for a long time. I adopt a more fascist approach and expire *everything*
older than 31 days, with      expire -I -e 31

Andy

-- 
Andy Clews, Computing Service, Univ. of Sussex, Brighton BN1 9QN, ENGLAND
JANET: andy@syma.sussex.ac.uk   BITNET: andy%syma.sussex.ac.uk@uk.ac
Voice: +44 273 606755 ext.2129