Axb wrote
> On 10/23/2014 05:03 PM, Jesse Stroik wrote:
>> Martin (and others),
>>
>>
>>> As others have already said, URI body rules use a list of valid TLDs to
>>> help with recognising URIs embedded in body text and this list is
>>> currently hardcoded into SA.
>>
>>
>> Thank you for the explanation and the rule. I've put it in place and it
>> appears to work fine with my first set of tests.
>>
>>
>>> which I've tested fairly carefully. All the subrules except __MG_TLD1
>>> work exactly as I wanted them to. I can live with __MG_TLD1 not working
>>> until either a current SA maintenance version is released with an
>>> extended list of hardcoded TLDs or a version using a configurable list
>>> appears.
>>
>>
>> I suspect they'll allow a configurable list of TLDs going forward.
> 
> As there's a bunch of other new TLDs being abused I would higly recomend 
> updating RegistrarBoundaries.pm
> from
> 
> http://svn.apache.org/repos/asf/spamassassin/trunk/lib/Mail/SpamAssassin/Util/RegistrarBoundaries.pm
> 
> on a Redhat flavour it goes in:
> 
> locate RegistrarBoundaries.pm
> /usr/local/share/perl5/Mail/SpamAssassin/Util/RegistrarBoundaries.pm
> 
> I updated this file yesterday.
> 
> btw, the file includes instructions so you can update your own file 
> without depending on a SA dev remembering to do it.
> 
> h2h
> 
> Axb

With approximately  two thousand new top-level domains
<https://gtldresult.icann.org/application-result/applicationstatus/viewstatus>  
in the queue for delegation this method of manually documenting validity is
not going to scale well. I've had some luck catching this junk by adding
blacklist_from directives to /etc/spamassassin/local.cf, like this:

blacklist_from *@*.link

This requires manual effort, too, but I can target it to specific problem
domains.



--
View this message in context: 
http://spamassassin.1065346.n5.nabble.com/link-TLD-spammer-haven-tp112305p112502.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Reply via email to