🚀 go-pugleaf

This one is fairly straightforward.  MMDF returns mail after it has been queued
for some amount of time.  Things get interesting when someone sets the system
date far ahead of the present.  Note the date on the Via: line.

Received: From washington.arpa.arpa by csnet-relay via smtp; 
          12 Apr 84 18:16 EST
Return-Path: <dave@wisc-rsch.arpa>
Received: from wisc-rsch.arpa by WASHINGTON.ARPA with TCP; Thu 12 Apr 84 14:19:31-PST
Date: Thu, 12 Apr 84 16:21:25 cst
From: Dave Cohrs <dave%wisc-rsch.arpa@csnet-relay.csnet>
Message-Id: <8404122221.AA11640@wisc-rsch.arpa>
Received: by wisc-rsch.arpa (4.22/3.7)
	id AA11640; Thu, 12 Apr 84 16:21:25 cst
To: laser-lovers%washington.arpa@csnet-relay.csnet
Subject: ln01 fonts and programs available
ReSent-date: Thu 12 Apr 84 15:04:27-PST
ReSent-from: Richard Furuta <Furuta%washington.arpa@csnet-relay.csnet>
ReSent-to: "Laser Lovers": ;
Via:  rand-relay; 5 Aug 84 15:44-PDT



Here's March's entry in the contest:

Date:     Tue, 13 Mar 84 6:58:04 EST
From:     CSNET-RELAY Memo Service (MMDF) <mmdf@CSNET-RELAY>
Subject:  Waiting mail
To:       chris%umcp-cs@Csnet-Relay.ARPA
Via:  CSNet-Relay; 13 Mar 84 22:51-EDT

    After 9 days (194 hours), your message has not yet been
fully delivered.  Attempts to deliver the message will continue
for 178956969 more days.  No further action is required by you.

    Delivery attempts are still pending for the following address(es):

	eggert @ Ucsb (queue: ucsb)

    Problems usually are due to service interruptions at the receiving
machine.  Less often, they are caused by the communication system.


			-- Dan