Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!linus!decvax!decwrl!sun!gnu
From: gnu@sun.uucp (John Gilmore)
Newsgroups: net.news.b
Subject: Re: expire takes 73 minutes of cpu?!?!?
Message-ID: <1802@sun.uucp>
Date: Thu, 22-Nov-84 00:50:00 EST
Article-I.D.: sun.1802
Posted: Thu Nov 22 00:50:00 1984
Date-Received: Fri, 23-Nov-84 02:28:59 EST
References: <1828@nsc.UUCP> <>, <1859@nsc.UUCP> <3114@utah-cs.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 15

The problem here is that there are two algorithms for expiration date:

(1) messages without Expires:
	take receipt date, add "-e" value or DFLTEXP if none was used.

(2) messages with Expires:
	use the specified date

So, it sounds to me like the info you need in the history file is:

(A)	Was Expires: specified?
(B)     if A==no,  the receipt date
	if A==yes, the specified expiration date

Then you'll never need to look in the message to finger out either case.