At 08:45 2000-09-28 -0700, Collin Park wrote:
I might also suggest adding the -F flag to grep (or using fgrep)... so
that foo.com in $FROM doesn't match foodcom.com in trusted_addresses.
Indeed. Good thing I normally use fgrep in my own rules.
Continuing the thread of useful greppage:
* $? $FORMAIL -xFrom: | $FGREP -i -f $PMDIR/friends.dat
This will match the words in friends.dat against the From:
Optionally, you may elect to add email addresses to the friends.dat in
formats other than complete email addresses of the form
username(_at_)domain(_dot_)tld(_dot_) You could add a generic "accept all mail from this
domain" using:
@foo.com
Excepting of course when there are hosts involved, in which case you could
instead specify:
.foo.com
(the converse is true if you're using these specifications for a twitlist -
you'd refuse mail from these domains reguardless of the username within
that domain).
Likewise, you can specify a generic email address - like "friends@", which
seems popular for spam.
Because on MY notwit rules, I don't limit the scanned header to just the
FROM, I can include optional HEADERS to check for - say my bypass header
inserted by a manually-invoked procmail filter that will extract messages
on a one-time basis from a twit or spam filtered file and inject it into my
regular mailstream:
X-xx-BYPASS: datecode
(use of a datecode limits forgeability should someone discover the header
format - periodically it gets changed when I'm revising rules).
---
Please DO NOT carbon me on list replies. I'll get my copy from the list.
Sean B. Straw / Professional Software Engineering
Post Box 2395 / San Rafael, CA 94912-2395
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail