Hi all,
I have a system-wide procmailrc file that performs various generic
SPAM-killing functions. A user recently subscribed to a mailing-list that
gets posts that are currently flagged by my filters as SPAM, and hence
killed. What I therefore want is to give the user control over the SPAM
filtering of this email using their own $HOME/.procmailrc file.
So basically, what I want is a recipe in my system-wide procmailrc file
with an action that causes the mail to be immediately delivered, through the
user's .procmailrc file. Diagramatically, it looks like this:
/etc/procmailrc
-----------
|
|
recipe to catch list-originated email -----> $USER/.procmailrc
|
|
system-wide SPAM killers
------------
I've considered using formail to add a "skip-me" header, but then I have to
ensure that every SPAM-killer recipe checks for it. If I add a new
SPAM-killer later, and forget to check, then mails will suddenly go missing.
So, I built a recipe that looks something like this:
generic recipe
-----------
:0
* ^TO_.*(spammy-list(_at_)spammy-host | @spammy-list)
| procmail <args>
-----------
Sadly, I have experienced great trouble in getting this to work. I have it
actually processing correctly at the moment, but not in a deployable manner
(see separate posting with subject: "problems piping to procmail").
So my question is:
Q: Are there any other ways I can use to cause procmail to branch before the
end of one procmailrc file, and begin processing using a different file
instead?
In case it's important, I am running RedHat 7.0, with procmail 3.14.
Thanks in advance for all help,
Cheers
Nik
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail