https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7256
Karsten Bräckelmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Karsten Bräckelmann <[email protected]> --- You are both correct, RW and Amir. The eval() rule is the same in URI_HOST_IN_BLACKLIST and its HEADER_* counterpart (one variant is just a named shortcut to the general check_uri_host_listed() function). With eval() rules, defining the rule as header or body does NOT limit the eval function's scope but determines only which part of the message the rule's score should be accounted for. Minimal test case: Ad-hoc message with no headers, header-body separator, and a URI in the body. Fed to spamassassin with a user URI blacklist option of the entire TLD .org. $ echo -e "\n\n spamassassin.apache.org" | ./spamassassin -L --cf="blacklist_uri_host org" Relevant header excerpt showing the _REPORT_ template tag rules's hit: X-Spam-Report: * 100 HEADER_HOST_IN_BLACKLIST Host or Domain in header is listed in the * user's URI black-list * [URI: spamassassin.apache.org (org)] * 100 URI_HOST_IN_BLACKLIST BODY: Host or Domain is listed in the user's * URI black-list * [URI: spamassassin.apache.org (org)] Removed HEADER_HOST_IN_BLACKLIST and *_WHITELIST rules. Committed to trunk and stable 3.4 branch respectively. Sending rules/60_whitelist.cf Committed revision 1812594. Sending rules/60_whitelist.cf Committed revision 1812595. Closing RESOLVED FIXED. -- You are receiving this mail because: You are the assignee for the bug.
