Re: TLD rules catch non-domain data

2021-08-20 Thread Kenneth Porter
On 8/20/2021 1:53 PM, Greg Troxel wrote: I just had it falsely hit, in that it triggered on mail that was ham. There was a .club URL, but it was to a club website mentioned in mail that I actually agreed to get and that was on topic. So I would suggest that rules that do not show actual evidence

Re: TLD rules catch non-domain data

2021-08-20 Thread Greg Troxel
Kenneth Porter writes: >> *  5.0 KAM_SOMETLD_ARE_BAD_TLD .stream, .trade, .pw, .top, .press, >> *  .guru, .casa, .online, .cam, .shop, .club & .date TLD >> Abuse > > The KAM rule was just recently fixed. If you have an example that's > still tripping it, post it to a pastebin and sh

Re: TLD rules catch non-domain data

2021-08-20 Thread Kenneth Porter
On 8/20/2021 6:23 AM, Matus UHLAR - fantomas wrote: it seems that some TLD rules catch strings that are not domains: *  2.0 PDS_OTHER_BAD_TLD Untrustworthy TLDs *  [URI: ups.mfr.date (date)] *  5.0 KAM_SOMETLD_ARE_BAD_TLD .stream, .trade, .pw, .top, .press, *  .guru, .c

TLD rules catch non-domain data

2021-08-20 Thread Matus UHLAR - fantomas
Hello, it seems that some TLD rules catch strings that are not domains: * 2.0 PDS_OTHER_BAD_TLD Untrustworthy TLDs * [URI: ups.mfr.date (date)] * 5.0 KAM_SOMETLD_ARE_BAD_TLD .stream, .trade, .pw, .top, .press, * .guru, .casa, .online, .cam, .shop, .cl