On Fri, Nov 28, 2003 at 10:33:27PM +0700, Tim Rice wrote:
In your message dated Thu, 27 Nov 2003 22:42:41 +0100, Dallman said that ...
On Thu, Nov 27, 2003 at 10:50:30PM +0700, Tim Rice wrote:
# Deliver Whitelist addresses
:0
* ?formail -x"From:" -x"Sender:" \
-x"Reply-To:" -x"Return-Path:" \
| fgrep -is -f $HOME/whitelist
{
:0 hif
| formail -A"X-Puremail: Global Whitelist"
:0
$DEFAULT
}
Tim, you will have a problem with overmatching on this. For
example, if I were looking for my own email address (dman@) and had
it in the whitelist, but then got mail from someone named feldman@
or sandman@ or freedman@ or goldman@ or whatever, it would match.
In fact, I just tried it to be double-sure.
I understand this if using "dman@" only in the whitelist, but what if
the whitelist had dman(_at_)whatever(_dot_)com(_dot_) Would my recipe still
match the
other dmans(_at_)somethingelse(_dot_)com?
I only typed "dman@" because I didn't feel like typing the domain
over and over. No, "whatever" won't match "somethingelse".
(But "whatever.com" could match "whatever.combatants.net".)
My point was that if "dman(_at_)aol(_dot_)com", for example, is in your
whitelist but a spammer pretends to be "goldman(_at_)aol(_dot_)com", it
will get through.
--
dman
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail