On Jul 10, 2006, at 4:25 PM, Dallman Ross wrote:
Your diagnosis of the problem isn't quite right. Procmail isn't
treating formail as a folder, despite that rather cryptic log message.
Moreover, the recipe you show above cannot be the one generating that
log message.
you're right, it wasn't - I'll paste the real log message below after
having made your suggested changes.
First, your recipe above has the letter "o" where you would need a
zero ("0") to start a procmail recipe on the initiating line.
this is my "new" recipe:
:0fwh:
* ^X-Spam-Status.*YES
* !^X-Spam-Status.*NO
|formail -I"Status: RO"
this is the log output as a result:
----
procmail: Couldn't determine implicit lockfile from "formail"
From reginald(_at_)funeasy(_dot_)biz Tue Jul 11 09:39:48 2006
Subject: We cure any desease!
Folder: /var/mail/lev
----
Since that is nothing like what you show, I again conclude that you
are pasting in inaccurate information into your query to the list.
Please don't do that!
apologies
If I fix the quotation marks around the formail statement, everything
works fine.
am I still missing something above?
Finally, your conditions seem silly to me. Why have a condition that
says to look for a "YES", then have a second condition that says to
look for the absense of a "NO"? I would think you could do the whole
thing with only one condition, better formulated.
yeah, me too - I slapped that together really quick - I found that
the first rule failed some messages, but will revisit that after I
fix this "problem".
thanks,
-lev
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail