You can try replacing your RegistrarBoundaries.pm file with the one from trunk. It should be kept up-to-date with the latest TLD craze. As far as I know, it hasn't been tested with 3.2.2 but should work nonetheless.
http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Util/RegistrarBoundaries.pm?revision=1633582&view=markup Kind regards, Peter Overtoom On 22 October 2014 20:46, Ken Bass <kb...@kenbass.com> wrote: > > On 10/22/2014 2:40 PM, Jesse Stroik wrote: > >> I noticed URLs from the TLD .link aren't properly classified on my mail >> server. I wrote a simple URI rule to recognize that TLD which never >> matched. I wrote a similar body rule, which did properly match. >> Interestingly, I do see DNS queries going out for the URLs in question. >> >> This is sa 3.3.2-4 -- is it a known issue? The URL in question is on a >> single line and is easily pulled out with egrep and properly parsed with >> the body rule. >> >> > 3.3.2 does not work with tlds that are not hardcoded into the software. I > signed up on this list last week with the same complaint (.link and > .website) are the latest spam havens. > Apparently even 3.4 does not address this yet, but is being address in the > future. Since I use Centos 7 which ships with 3.3.2, it creates a problem > for me, meaning unless backported, I'm kinda stuck. > > What is a bit frustrating is that the URI rules will work for emails that > are HTML encoded, but not for plain text emails. So I was pulling my hair > out trying to figure out why my rules were working sometimes and not others. >
