At 10:46 2002-05-03 -0700, Edward Huang did say:
thank you very much. the solution was to enclose all the ORing with ( )
False positive has gone down to only 5-10 a day (can you believe how often
F--K and S-X comes up in everyday conversation?)
You might consider greenlisting the people who you consider these terms to
be appropriate conversation with - IME, I only talk about s-x topics with
close friends and intellectuals, a list which is easy enough to set aside
if it were to become necessary. By greenlisting some addresses -
prefiltering them, or at least saying "if the From: matches one of these,
SKIP the spam checks," then your false positives will drop significantly.
For instance, I filter twits before filtering just about anything else
(because twits are everywhere!), then I filter "exclusive" lists - those
which have a closed membership and limit posts to subscribers, are
comprised solely of friends, or which are moderated or outbound
notification lists only - and then I filter for spam, and then for generic
mail and lists.
Since the procmail list itself allows non-subscriber submissions, it gets
filtered post-spam.
I need to EMAIL spam and adult to a mailbox
Email? They're not on the local host?
Just dumping to folder results in 'invalid mail format'
Dunno about mutt, but elm uses mbox - i.e. NOT maildir (which is what I
generally associate with the term "folders" in an email context).
What program is complaining about this? Do the messages lack a "From " header?
One related locking issue, the procmail LOG File. how to perform locking
there (there are multiple sendmail and procmail forks running) so the
file doesnt get messed up?
Yes, log entries get a bit interlaced. I don't know of any way to lock it
from a script short of putting a LOCKFILE statement at the top of your
procmailrc THEN enabling locking - but that gets ugly when you have lots of
email.
Sometimes I've thought it would be nice if procmail had the capability to
"batch" log activity to a buffer so that it could output it in one lump, or
to use a syslog type facility.
lastly, is there a LOG option such that it will show only the MATCHED
receipe and not all the unmatched receipes? that would save a LOT of disk
space !!
When you're VERBOSE logging, it's because you want to see the detail of all
the recipes leading up to the delivery action - often, it's the recipes
that DON'T match which are important.
You can turn VERBOSE ON and OFF where needed. Sometimes you just want
verbosity around a specific recipe that you're debugging (though a sandbox
is much better for this), or you want log detail on some scoring operation
- so just put VERBOSE=ON before the recipe, and VERBOSE=OFF after it.
If you want to log other info, you can use the LOG= statement:
:0
* somecondition
{
LOG="Action: Jarvis is being inconsiderate again$NL"
:0:
jarvis.junk.mbx
}
Or whatever. I log my spam catches in a similar fashion.
I archive my compressed mailboxes and their logfile periodically (did that
just yesterday in fact).
A procmail book I'd like to recommend to all is
Martin McCarthy
FTR, Martin is a contributor on this list.
[kerchomp]
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail