Path: utzoo!utgpu!water!watmath!clyde!cbosgd!osu-cis!tut!mumble!karl
From: karl@mumble.cis.ohio-state.edu (Karl Kleinpaste)
Newsgroups: news.software.b
Subject: Expire "unparsable date" should tell me what article was botched
Message-ID: <3258@tut.cis.ohio-state.edu>
Date: 16 Dec 87 15:40:16 GMT
Sender: news@tut.cis.ohio-state.edu
Lines: 23

For the past several days, I and the other folks that expand in the
"news" alias here have been getting the following little jewels in our
mailboxes every morning, courtesy of the script I use to expire news:

	Date: Wed, 16 Dec 87 06:26:44 EST
	From: root@tut.cis.ohio-state.edu
	To: news@tut.cis.ohio-state.edu
	Subject: Expire errors

	expire: Unparsable date "31 Dec 69 23:59:59 GMT"

We get one of these from Tut, the main departmental news server
machine, and osu-cis, the 3B2 that does UUCP gatewaying for us.  I
have no objection to expire complaining about a nonsensical date; and
I suppose that this date qualifies as nonsensical because it's before
the "epoch."  But I really, REALLY wish it would tell me something
more about the article it didn't like; at least tell me the
Message-ID, preferably its filename in the news spool area, so I can
go blow it away, or change its Date: or Expires: line, or SOMETHING.

Prettyplease?  For patch #15?  Maybe?
-=-
Karl