Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!unmvax!ogccse!schaefer
From: schaefer@ogccse.ogc.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: dead.letter twist
Message-ID: <4540@ogccse.ogc.edu>
Date: 3 Sep 89 23:59:20 GMT
References: <24FF7EB4.54ED@drivax.UUCP>
Reply-To: schaefer@ogccse.UUCP (Barton E. Schaefer)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 31

In article <24FF7EB4.54ED@drivax.UUCP> davison@drivax.UUCP (Wayne Davison) writes:
} Here's a twist on the handling of "dead.letter" that I just noticed NN
} using:  when a dead letter is produced, the previous contents of dead.letter
} are first appended to the file "dead.letters", leaving only the most recent
} failure in dead.letter.  This is kinda nice, if only to save you a little
} editing when processing the last dead message.
} 
} Anybody else like this idea?  Anyone want to see it supported in mush?
} Or is there some way to do it already?

You can always

	set dead = '|dead.script'

where dead.script is something similar to

	#! /bin/sh
	dead=$HOME/dead.letter
	if [ -f $dead ]
	then
	    touch ${dead}s	# create it if it isn't there
	    cat $dead >> ${dead}s
	fi
	cat > $dead

Of course you probably want to make it a little more careful than that.
-- 
Bart Schaefer           "And if you believe that, you'll believe anything."
                                                            -- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer