Re: top and other spammy TLDs

2017-02-25 Thread Paul Stead
On 25/02/2017, 00:39, "Alex" wrote: header PDS_FROM_OTHER_BAD_TLD eval:check_from_in_list('NEWSPAMMY') This particular check will not work as the current release of SA does not include the improvement in the BZ report. If you have the patch included (I can’t

Re: top and other spammy TLDs

2017-02-24 Thread Alex
Hi, On Fri, Feb 24, 2017 at 7:33 PM, Benny Pedersen wrote: > Alex skrev den 2017-02-25 01:18: > >> Is there something more that needs to be done than the above? > > > what sa version ? > > i know it works with 3.4.1 > > but have disabled my own rules again This is a relatively

Re: top and other spammy TLDs

2017-02-24 Thread Benny Pedersen
Alex skrev den 2017-02-25 01:18: Is there something more that needs to be done than the above? what sa version ? i know it works with 3.4.1 but have disabled my own rules again

Re: top and other spammy TLDs

2017-02-24 Thread Alex
Hi, On Tue, Feb 21, 2017 at 12:57 PM, Paul Stead wrote: > I’ve posted this before, this is how I manage these nasty TLDs: > > Make sure WLBLEval is enabled: > > loadplugin Mail::SpamAssassin::Plugin::WLBLEval > > Then add the TLDs to a URI_HOST list: > >

Re: top and other spammy TLDs

2017-02-22 Thread RW
On Tue, 21 Feb 2017 18:41:08 + RW wrote: > On Tue, 21 Feb 2017 17:57:13 + > Paul Stead wrote: > > > I’ve posted this before, this is how I manage these nasty TLDs: > > > > Make sure WLBLEval is enabled: > > > > loadplugin Mail::SpamAssassin::Plugin::WLBLEval > > > > Then add the TLDs

Re: top and other spammy TLDs

2017-02-21 Thread Paul Stead
On 21/02/2017, 23:15, "Paul Stead" wrote: I can’t see how this can be the same for the check_from_in_list calls, however? Apologies – it is not possible to add custom addrlists in SA - https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7354 -- Paul Stead

Re: top and other spammy TLDs

2017-02-21 Thread Paul Stead
On 21/02/2017, 18:41, "RW" wrote: On Tue, 21 Feb 2017 17:57:13 + Paul Stead wrote: > I’ve posted this before, this is how I manage these nasty TLDs: > > Make sure WLBLEval is enabled: > > loadplugin

Re: top and other spammy TLDs

2017-02-21 Thread RW
On Tue, 21 Feb 2017 17:57:13 + Paul Stead wrote: > I’ve posted this before, this is how I manage these nasty TLDs: > > Make sure WLBLEval is enabled: > > loadplugin Mail::SpamAssassin::Plugin::WLBLEval > > Then add the TLDs to a URI_HOST list: > > enlist_uri_host (NEWSPAMMY) top The

Re: top and other spammy TLDs

2017-02-21 Thread Paul Stead
I’ve posted this before, this is how I manage these nasty TLDs: Make sure WLBLEval is enabled: loadplugin Mail::SpamAssassin::Plugin::WLBLEval Then add the TLDs to a URI_HOST list: enlist_uri_host (NEWSPAMMY) top enlist_uri_host (NEWSPAMMY) date enlist_uri_host (NEWSPAMMY) faith

Re: top and other spammy TLDs

2017-02-20 Thread John Hardin
On Mon, 20 Feb 2017, Alex wrote: Hi, Some time ago I had put together a rule based on comments from this list, and I've identified a FP that I hoped someone could help me to correct. The full domain in the email was http://www.top-1.biz. However, it's being tagged as if it's "top" as the TLD

top and other spammy TLDs

2017-02-20 Thread Alex
Hi, Some time ago I had put together a rule based on comments from this list, and I've identified a FP that I hoped someone could help me to correct. The full domain in the email was http://www.top-1.biz. However, it's being tagged as if it's "top" as the TLD in one of KAMs rules and one of