1) get an email that really matches and one that is forged
-or-
2) save an email in mbox format and hand-edit the headers to create 2 new emails, one that looks like a real mail and one that's a forgery. Run those through spamassassin -t.
So if I was going to whitelist_from_rcvd you I'd have a rule:
whitelist_from_rcvd [EMAIL PROTECTED] sonic.nmgi.com
I'd spamassassin --lint -D to make sure I had no typoes in the rule (ie: mis-spelling whitelist as whitlist)
If I was paranoid and wanted to test it (beyond the lint) I'd then run the email you just sent the list through, make sure it matches
spamassassin -t < dallasmail.mbx
then I'd edit the "sonic.nmgi.com" in the received headers to be something else, like "mx1.mail.yahoo.com" and run it again, and make sure that it's not whitelisted.
Received: from sonic.nmgi.com ([64.217.128.161] helo=exchange.nmgi.com)
by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
id 18OJoO-0007HU-00
changed to:
Received: from mx1.mail.yahoo.com ([64.157.4.83] helo=mx1.mail.yahoo.com)
by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
id 18OJoO-0007HU-00
spamassassin -t < dallasforge.mbx
At 09:39 AM 12/17/2002 -0600, Dallas Engelken wrote:
Can anyone give me a recommendation on how I can test a whitelist_from_rcvd rule?
Thx
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
