🚀 go-pugleaf

In article <7306@ingr.com>, fordke@ingr.com (Keith Ford x8614) writes:
>
> I read news, reply to news, and post news from uunet!ingr but my
> base system is at uunet!ingr!b23b!dragon.  How can I have mail
> that is sent to uunet!ingr automatically bounced to my base?

According to david@ms.uky.edu (David Herron -- One of the vertebrae):
>On Sendmail machines you instead place a ".forward" file in your home
>directory which gives an address to which to send the mail.  I believe
>you can also pipe into a process from the ".forward" file.

The ".forward" feature is supported by Sendmail, Smail 2.5 and Smail 3.
Sendmail and Smail 3 support pipe aliases in ".forward" and elsewhere.
Smail 2.5 doesn't do pipes; if you want them you should get Deliver 2.0.
But even with Deliver installed I just use the ".forward" file for simple
forwarding, since Deliver doesn't know about "user@host" (yet :-)).

>On MMDF sites you can do some rule-based matching on various
>header lines and have actions available which will junk the
>message, append it to a file, or pipe it into a process.  The
>same file & file-format work with "mh" users.

This is rather like what Deliver has, except that Deliver's behavior isn't
rule-based.  Rather, Deliver runs a user-written shell script to determine
what to do, or sometimes actually to do it.  For example:

	:
	# /usr/sample/.deliver

	user="$1"

	# I don't want mail about AMWAY
	# (I use the "header" utility, included with Deliver)

	if header -f subject $HEADER | grep -si "amway"
	then
	     echo DROP
	     exit
	fi

	# On weekends, forward this mail to the home machine

	case `date "+%w"` in
	0|6)    echo "homesite!myname"; exit ;;    # Deliver knows about UUCP
	esac

	# Okay, just drop it in my default mailbox.

	echo "$user"

>I'm sure "deliver" has something neat and wonderful which that
>Chip fella will tell us about.

In all honesty, I wasn't going to say anything until I saw this.  :-)
-- 
You may redistribute this article only to those who may freely do likewise.
Chip Salzenberg at A T Engineering;  <chip@ateng.com> or <uunet!ateng!chip>