On 10/28/2014 10:30 PM, Kevin A. McGrail wrote:
On 10/28/2014 5:19 PM, Axb wrote:
On 10/28/2014 10:13 PM, Kevin A. McGrail wrote:
On 10/28/2014 12:06 PM, Axb wrote:
Patience quota exceeded.
What a weird way to get a new TLD's ROI
if (version >= 3.004000)
blacklist_uri_host link
endif
So we added this wanting to play with this command and had no change in
behavior for an email with this from header:
From: "Notification" <notification@22notification-munge.linkmunge>
But no use of .linkmunge domains in the body
Expected, yes?
It should tag blubber[[.]]link
Interesting. Ok, definitely not hitting just a from with a [[.]]link
email address for me. Can you test that.
Are you sure you're using an updated RegistrarBoundaries.pm ?
Running trunk with your TLD updates, yes.
before I commit please test with
(BEWARE LINE BREAKS IN RULES!!!)
body URI_HOST_IN_BLACKLIST eval:check_uri_host_in_blacklist()
describe URI_HOST_IN_BLACKLIST domain is in the URL's black-list
tflags URI_HOST_IN_BLACKLIST userconf noautolearn
score URI_HOST_IN_BLACKLIST 100.0
body URI_HOST_IN_WHITELIST eval:check_uri_host_in_whitelist()
describe URI_HOST_IN_WHITELIST domain is in the URL's white-list
tflags URI_HOST_IN_WHITELIST userconf noautolearn
score URI_HOST_IN_WHITELIST -100.0
header HEADER_HOST_IN_BLACKLIST eval:check_uri_host_listed('BLACK')
describe HEADER_HOST_IN_BLACKLIST Whitelisted header host or domain
tflags HEADER_HOST_IN_BLACKLIST userconf noautolearn
score HEADER_HOST_IN_BLACKLIST 100.0
header HEADER_HOST_IN_WHITELIST eval:check_uri_host_listed('WHITE')
describe HEADER_HOST_IN_WHITELIST Blacklisted header host or domain
tflags HEADER_HOST_IN_WHITELIST userconf noautolearn
score HEADER_HOST_IN_WHITELIST -100.0
you should see something like
* 100.0 HEADER_HOST_IN_BLACKLIST Host or domain found in URI is
blacklisted
* [URI: www.bupahif.link (link)]
* 100 URI_HOST_IN_BLACKLIST BODY: domain is in the URL's black-list
* [URI: www.bupahif.link (link)]
thanks
Axb
