From dattier@sashimi.wwa.com Fri Jan 24 01:04:11 1997
Path: fu-berlin.de!news.mathworks.com!news.sprintlink.net!news-peer.sprintlink.net!news.wwa.com!not-for-mail
From: dattier@sashimi.wwa.com (David W. Tamkin)
Newsgroups: comp.mail.misc
Subject: Re: Procmail alternative anyone?
Date: 23 Jan 1997 17:23:52 -0600
Organization: TIPFKAG  [World-Wide Access, Chicago, Illinois  60606-2804]
Lines: 26
Message-ID: <5c8ru9$qid@miso.wwa.com>
References: <32f12f31.55674305@news.alt.net> <5c3lc7$ajv@samba.rahul.net> <wx0zpy1xwup.fsf@sws5.CTD.ORNL.Gov> <5c62bv$3un@samba.rahul.net>
NNTP-Posting-Host: miso.wwa.com

Michelle Dick <artemis@rahul.net> wrote in <5c62bv$3un@samba.rahul.net>:

D> In article <wx0zpy1xwup.fsf@sws5.CTD.ORNL.Gov>,
D> Dave Sill  <de5@sws5.ctd.ornl.gov> wrote:

S> Sure. Deliver just runs a script you provide

D> I thought so.  Deliver is therefor not as powerful as procmail. To do
D> the same stuff, you have to write it yourself or hire someone to do so.

Actually, deliver recognizes a #! line at the top of ~/.deliver, so a
procmail fan can write a ~/.deliver that looks like this (the -f- is a
common usage but is not required):

#!/path/to/procmail -f-

[followed by whatever procmailrc code he or she pleases]

so you can make deliver turn out *exactly* as powerful as procmail. 
Likewise, a deliver fan could write a ~/.procmailrc like this:

 :0
 | /path/to/deliver

and put anything he or she pleases into ~/.deliver.