the documentation for whitelist_from_rcvd doesnt make sense to me.

"Use this to supplement the whitelist_from addresses with a check against the Received 
headers. The first parameter is the address to whitelist, and the second is a domain 
to match in the Received headers. This does not allow globbing, and must be followed 
by a numeric IP address in brackets."

It says "this does not allow globbing", yet the whitelist_from_rcvd entries in 
60_whitelist.cf are glob patterns.  Is that only referring to the domain listed in the 
received header that has no glob support?

how is it possible to test a custom whitelist_from_rcvd rule?   i generated one using 
the example

[EMAIL PROTECTED] spamassassin]# cat 63_wl_test.cf 
whitelist_from_rcvd [EMAIL PROTECTED]  example.com

and tried to test it using

[EMAIL PROTECTED] spamassassin]# telnet mailgw 25
mail from: [EMAIL PROTECTED]
rcpt to: [EMAIL PROTECTED]
data
From: [EMAIL PROTECTED]
.

yet, it doesnt get whitelisted.  looking at the headers on the message, i see the 
first received header as,

Received: from unknown (64.217.128.174)

I believe the "unknown" is where the whitelist_from_rcvd pulls the second part of it's 
rule, is that correct??  If I add a HELO into my SMTP communication, the recieved 
header changeds to

#############
continuing from a premature send (damn CTRL+ENTER)
#############

Received: from unknown (HELO example.com) (64.217.128.174)

Yet, it still does not whitelist.  What is the deal with that unknown? 

Dallas


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to