procmail
[Top] [All Lists]

Re: Can These 2 Recipes Be Or'd?

2004-05-09 19:40:13
Thanks for reply - middle post reply.

On Mon, 2004-05-10 at 09:12, Dallman Ross wrote:
On Mon, May 10, 2004 at 08:23:07AM +1000, Marvin R. Pierce wrote:
Wondering it these can be combined into a single recipe?

:0:
* 
^(To|Cc|Bcc).*(xxxxxxx(_at_)teebookglobal(_dot_)com|xxxxxxx(_at_)303Sport(_dot_)com)
/dev/null

:0:
* ^Received:.*boxer\.([a-z0-9_-]+\.)?com\.au
spam/

I presume you would send to spam/ in either case.

Yes


You have a problem with lockfiles in both recipes above, btw.  In
the first, you do not want a lockfile for /dev/null.  In the second,
you do not want a lockfile for a maildir-style folder.

I've removed all :0: or :0 <flags>: in recipes



How to OR in procmail has been discusses many times, so you might
want to search the archives for case-sensitive "OR".  But basically
there are three ways to do it.  The first is very ugly, and I don't
recommend it:

I'll do a search to learn more. Trying to sort things out after a crash
and ensure everything is running correctly.


 :0  f l a g s
 * ^((To|Cc|Bcc).*xxxxxxx@(teebookglobal|303Sport)[.]com|\
      Received:.*boxer[.]([a-z0-9_-]+[.)?com[.]au)
 spam/


The second way uses scoring, for which see "man procmailsc".
We use a number of at least 2**31-1 to get procmail to skip
right to the action line in a case where a weighted condition
matches (evaluates true):

 :0  f l a g s
 * 9876543210^0  first condition
 * 9876543210^0  second condition
 spam/

I've tried:
#303Sport MAIL          Send 303Sport mail to spam
:0
* 9876543210^0
^(To|Cc|Bcc).*(xxxxxxx(_at_)teebookglobal(_dot_)com|xxxxxxx(_at_)303Sport(_dot_)com)
* 9876543210^0 ^Received:.*boxer\.([a-z0-9_-]+\.)?com\.au
/dev/null

Seems to be working correctly. 


The third way uses "reverse De Morgan" logic to accomplish an OR
by way of "not A  AND  not B":

 :0  f l a g s
 * ! first condition
 * ! second condition
 { }  # do nothing

 :0 E  # else
 spam/


Okay, that's two recipes again, but it's still useful to rely on
sometimes.

One more thing...
In my pmlog file, I have and I am wondering if this is a problem with formail 
that I need to fix:

procmail: [10402] Mon May 10 01:00:04 2004
procmail: Couldn't determine implicit lockfile from "formail"
procmail: Locking ".lock"
procmail: Executing "formail,-z"
procmail: Unlocking ".lock"
procmail: Match on "< 256000 "
procmail: Couldn't determine implicit lockfile from "/usr/bin/spamc"
procmail: Locking ".lock"
procmail: Executing "/usr/bin/spamc"
procmail: [10402] Mon May 10 01:00:07 2004
procmail: Unlocking ".lock"
procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*"
procmail: No match on "^X-Spam-Status: Yes"
procmail: No match on "^^rom[ ]"
procmail: Extraneous locallockfile ignored
procmail: Couldn't determine implicit lockfile from "razor-check"
procmail: Locking ".lock"
procmail: Executing "razor-check"
procmail: [10416] Mon May 10 01:00:09 2004
procmail: Couldn't determine implicit lockfile from "formail"
procmail: Locking ".lock"
procmail: [10402] Mon May 10 01:00:15 2004
procmail: Non-zero exitcode (1) from "razor-check"
procmail: Assigning "LASTFOLDER=razor-check"
procmail: Unlocking ".lock"
procmail: Assigning "INCLUDERC=/home/mpierce/Procmail/rc.subscriptions"


_______________________________________________
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>