procmail
[Top] [All Lists]

new feature request in 3.22, pipes interpreted from variable expansion

2002-03-20 01:26:22

I had sent this to procmail-dev, but I'm not sure if they accept
email from non-subscribed people, so I thought I'd send it here
in case anyone knows a way I can work around this problem without
the enhancement request.

Here goes:

We are trying to set up using spambouncer which is a complicated
set of procmail scripts designed to eliminate spam.

What I would like to do is be able to configure a .procmailrc
file that can handle both mh and non-mh users as a front end
to the unmodified spambouncer procmail scripts.

In order to do this, a typical rule in spambouncer might
look like this:

  :0 Aw
  * !FILTER ?? yes
  ${BLOCKFOLDER}

In other words a variable is used to hold the name of the file
where blocked messages would go.

typically you might have something like this:

BLOCKFOLDER=${HOME}/Mail/blocked.incoming

but for MH, what I would like to do is this:

BLOCKFOLDER="| /usr/local/lib/mh/rcvstore +blocked"

In other words, the first character of the expanded variable
is a PIPE, so it'd be nice if the rule could expand the variable,
and if I pipe is found, try to use it.

This is not the current behavior:

/bin/sh: |: not found
/bin/sh: |: not found

Does this sound like a reasonable feature to implement?

If not, is there another way around this problem given that I don't
want to modify the original source files?
(so I can set up a weekly ftp script to download and unpack the
original source).

Thanks in advance,

-Dave

________________________________________________________________________
David Meleedy                           Analog Devices, Inc.
David(_dot_)Meleedy(_at_)analog(_dot_)com               Three Technology Way
Phone: 781 461 3494                     Norwood, MA  02062-9106  USA
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>