Xref: utzoo news.sysadmin:2441 news.admin:5878
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!elroy!usc!csun!csusac!unify!jwc
From: jwc@unify.UUCP (J. William Claypool)
Newsgroups: news.sysadmin,news.admin
Subject: Re: question on bad unparsable dates
Message-ID: <858@unify.UUCP>
Date: 4 Jun 89 04:01:12 GMT
References: <185@icdi10.UUCP> <730@dtscp1.UUCP> <455@focsys.UUCP> <7008@cbmvax.UUCP> <866@ks.UUCP>
Reply-To: jwc@unify.UUCP (J. William Claypool)
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 15

In article <866@ks.UUCP> kurt@ibmarc.UUCP (Kurt Shoens) writes:
>Several people have written about the Unparsable date error that they
>see running expire.  I, too, suffer from this (well I don't suffer much).
>I was curious about the phenomenon, so I grepped the whole news spool
>for the funny date and found 11 unique articles that contained the
>bad date string "31 Dec 69 23:59:59 GMT" (outside the discussion of the
>problem in news.admin).  They all use it as the "Expires:" date.  The

I have seen this date generated (apparently by inews) when an
unparsable date is supplied for the 'Expires:' header when editing the
article from Pnews for example.
-- 
Bill Claypool       (916) 920-9092 |
jwc@unify.UUCP                     |
{csusac,pyramid,sequent}!unify!jwc |