> > The main problem with this approach is that it requires monitoring
> > of the SPAM assassin tests being applied as the software is
> > updated...
>
> Well, I'd say this is a problem chiefly because whoever _is_
> administering the server -- not spamassassin.apache.org --
> The main problem with this approach is that it requires monitoring
> of the SPAM assassin tests being applied as the software is
> updated...
Well, I'd say this is a problem chiefly because whoever _is_
administering the server -- not spamassassin.apache.org -- is clearly
n
>
> Would it not be easier to create meta rules for the rules you
> are looking for, then simply add more points for those? Thats
> what most of us do. Otherwise you are prbly fighting a losing
> battle trying to get a standard naming scheme. Its a great
> idea, that simply won't get followed.
Title: RE: Naming conventions for tests
> -Original Message-
> From: Ben Kreunen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 22, 2006 8:07 PM
> To: SPAMAssassin email list
> Subject: Naming conventions for tests
>
>
> Hi All
>
> I've been a
Hi All
I've been approaching the problem of filtering spam at the email client end
using the SpamAssassin (3.x) header. Our email server (over which I have no
control) has a couple of server-side filters that reject emails with
infected attachments and messages with a spam score > 15. This leaves
