Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Subject: Re: myfanbox.com
From: Karsten =?ISO-8859-1?Q?Br=E4ckelmann?= <guenther@rudersport.de>
To: users@spamassassin.apache.org
In-Reply-To: <alpine.LNX.2.00.1111061117110.10571@athena.impsec.org>
References: <20111106182554.GZ26539@chaosreigns.com>
	 <alpine.LNX.2.00.1111061117110.10571@athena.impsec.org>
Content-Type: text/plain
Date: Sun, 06 Nov 2011 21:32:06 +0100
Message-Id: <1320611526.4883.7.camel@monkey>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sun, 2011-11-06 at 11:17 -0800, John Hardin wrote:
> On Sun, 6 Nov 2011, darxus@chaosreigns.com wrote:
> 
> > I'd like to get this added to the default rule set, any objections?

Yes, strong objections. SA is NOT a blacklist in any way.

Adding domains just like that is not what SA does. The update mechanism
is not meant to be a global large-scale game of whack-a-mole, including
new and changed domains.

> > header FROM_MYFANBOX From:addr =~ /\@myfanbox\.com$/i
> > score FROM_MYFANBOX 5
> 
> Not at that score.
> 
> I'll add it to my sandbox right now so we can see what happens.

Of course, fully agree on the score issue.

However, John, I strongly urge you NOT to include that rule in your
sandbox for stock. This is the wrong thing to do, and basically
contradicts everything SA stands for.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}