On Thu, Feb 14, 2008 at 02:32:26PM -0800, Professional Software Engineering
wrote:
FTR, the lockfile flag doesn't go at the outer nesting level - it belongs
on any recipe delivering to a mailbox. Also, I'd consider INVERTING the
delivery to default:
:0
* ^X-DSPAM-Result: Spam$
{
FROM=`formail -XFrom: | formail -r -xTo: | tr -d ' '`
:0:
* ! ? ~/scripts/address_ldap_search.pl $FROM
.Junk/
}
You might check my sandbox (see my .sig) and just extract a number of
common headers right off, then the rule could be simplified:
:0:
* ^X-DSPAM-Result: Spam$
* ! ? ~/scripts/address_ldap_search.pl $FROM
.Junk/
Hello,
Yea thats a better way todo it, guess I went in the wrong direction with that
one.
As for the lockfile flag I didn't know that you should have it on everything
that delivers to a mailbox, I will go through and check that :)
Live and learn.
Thanks for your help both of you,
Matt.
Either way, the idea is that if you have OTHER filters, they'll continue to
operate on the message, possibly delivering it to a mailbox OTHER than
$DEFAULT, which seems like a more desireable outcome.
Of course, lots of spam is forged to come from people you know, so this
ldap search is very likely to have at least a few spams filter through it.
---
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 homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
--
My software never has bugs. It just develops random features.
Matt Richards
signature.asc
Description: Digital signature
____________________________________________________________
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