I'm trying to refine a problem I ran into yesterday on a rule.
I believe that this is essentially correct and it is what I'm using today:
:0 HBW:
* ? razor-check
.razor_spam/
However, yesterday razor went offline for a while and the return code
was neither 0 or 1 as normally anticipated. What I was using yesterday
was essentially from the razor-check man pages:
:0 Wc
| razor-check
:0 Wa
/home/foo/Mail/razor-caught
Which does a great job of creating lots of duplicate emails. I've since
implimented the new razor-check rule above and the formail -D 8192
msgid.cache rule to capture duplicate emails, fwiw.
Using the first rule, if razor is offline again, it will simply fail to
identify any spam. However I think I can find the same type of problem
occurring for other scripts and am therefore trying to identify the
return code better.
I was having trouble with the basic process of capturing a return code
and comparing it with constants. All I'm really doing now is looking to
see if the return code is !=0 or =0. What I should probably attempt is
to check for 0, 1, or >1 and so on.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail