[Wlug] Procmail Question

[Marc Hughes]

With the locking (:0:) all seems to work now.  I'm guessing it's because
I have an IMAP connection open to the mailbox while I receive the new
email and it get's processed.  

While we're talking about procmail... A second question:

:0:
* ^From.*jenny@axte84\.com
* ^Subject.*MILLION OPT-IN EMAIL ADDRESSES
Badspam

This will do an AND between the two conditions ... Is there an easy way
to OR between them? ... Or do I need to make a separate rule for each
and every condition?  And an even further note... What are the thoughts
on some of these anti-spam tools that work with procmail?  Any
favorites?

Thanks a lot guys,
-Marc

-----Original Message-----
From: Theo Van Dinter [mailto:felicity@kluge.net] 
Sent: Friday, November 08, 2002 9:21 AM
To: wlug@mail.wlug.org
Subject: Re: [Wlug] Procmail Question


On Fri, Nov 08, 2002 at 09:13:18AM -0500, Peter Gutowski wrote:
> According to the man page the second ":" is optional, i.e.
> 
> :0:
> 
> but, as a sample of something known to work (from the SpamAssassin 
> sample .procmailrc) it does use the above syntax. Here's the example:
> 
> So maybe the second ":" is not optional all the time?

Just so we're all clear, the second ":" tells procmail that is needs to
lock the file before writing to avoid corrupted mailboxes.  So it's a
good idea if you're writing to a mailbox, but isn't actually required,
especially if you're writing to /dev/null or something.

I didn't see anything wrong offhand with the procmail rules shown.  Can
we see the header of an example mail which doesn't work with the
original but works with the carbon copy method?  (and by work, just to
double check, we're talking about the message going into the "test"
folder).

-- 
Randomly Generated Tagline:
"When it is not necessary to make a decision, it is necessary not to
make a
 decision."               - From www.slashdot.org