Xref: utzoo comp.mail.elm:1547 comp.mail.misc:1928
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!ateng!chip
From: chip@ateng.ateng.com (Chip Salzenberg)
Newsgroups: comp.mail.elm,comp.mail.misc
Subject: Re: Running a program for incomming mail
Message-ID: <1989May25.174014.5940@ateng.ateng.com>
Date: 25 May 89 21:40:14 GMT
References: <199690@hrc.UUCP>
Followup-To: comp.mail.misc
Organization: A T Engineering, Tampa, FL
Lines: 43

[followups directed to comp.mail.misc, since Elm is not involved]

According to dan@hrc.UUCP (Dan Troxel):
>I wish to create a mail archiver system. I have Elm 2.1 and Smail 2.5.
>How do I create a .forward file that will work with elm/smail to
>work automatically when a person sends mail to archive-request. When
>the mail goes to archive-request, it will check for a send command, and
>then send him/her the appropriate file.

The best solution here is Smail 3, but that's not available yet, so...

The "deliver" program is intended to provide just such a facility as this.
Deliver runs system-wide and/or user-specific shell scripts to determine how
to handle incoming mail.  For example, the following system delivery file
hands all "archive-request" messages to the archive server, and delivers
other mail normally.

	: deliver.sys
	# System delivery file

	for u
	do
	    case "$u" in
	    archive-server)     archive-program $FROM <$BODY ;;
	    *)                  echo $u ;;
	    esac
	done

Deliver can be picked up from ateng by anonymous UUCP.  Here are the files
in ~uucp/deliver:

  -rw-r--r--   1 network    26101 Feb 15 20:36 deliver.01.Z
  -rw-r--r--   1 network    18446 Feb 15 20:36 deliver.02.Z
  -rw-r--r--   1 network    21081 Feb 15 20:36 deliver.03.Z

Here is an L.sys (Systems) entry:

  ateng Any 2400 ACU 18138824934 ogin:--ogin:--ogin: nuucp

-- 
Chip Salzenberg             <chip@ateng.com> or <uunet!ateng!chip>
A T Engineering             Me?  Speak for my company?  Surely you jest!
	  "It's no good.  They're tapping the lines."