Xref: utzoo comp.mail.elm:2426 comp.mail.misc:3065
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!ziggy!usfvax2!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.mail.elm,comp.mail.misc
Subject: Re: Status question
Message-ID: <25FBC96E.4DA6@tct.uucp>
Date: 12 Mar 90 16:08:14 GMT
References: <4312@mace.cc.purdue.edu> <1990Mar5.171928.12129@DSI.COM> <1142@urbana.mcd.mot.com>
Organization: ComDev/TCT, Sarasota, FL
Lines: 28

According to darrell@urbana.mcd.mot.com (Darrell McIntosh):
>I use deliver to sort my incoming mail into many different files or my
>spool file.  I've hacked [Elm to treat all mailboxes like system mailbox].
>This allows me to be able to identify any mail that arrived
>since I last read the file.

There's no need to hack Elm for this purpose.  It just so happens
that, when Elm discovers a new message (status "N") and you don't read
it, it saves the message with status "O".  Furthermore, that status is
saved in the message header, with a line like this:

	Status: O

However, there's no reason why some other program can't insert that
line in Elm's behalf.  So (here it comes), if you use Deliver, you can
do it with your user delivery file:

	# We assume here that $box is a mailbox to receive the message

	( header -nv -f status $HEADER | grep -v '^$'
	  echo "Status: O"
	  echo ""
	  cat $BODY ) | deliver -b $box

Presto!  All newly arrived messages are neatly labeled "O" on the Elm menu.
-- 
Chip Salzenberg at ComDev/TCT   <chip%tct@ateng.com>, <uunet!ateng!tct!chip>
          "The Usenet, in a very real sense, does not exist."