My users can find the "14" and change it easier than counting *'s
and if I want to I can template the file and expand the correct score to
each user easier with a number than with a bunch of *'s
Jay Lee wrote:
Tim Litwiller wrote:
this is the way I've been doing it in procmail - then I don
On 7/12/05, Jay Lee <[EMAIL PROTECTED]> wrote:
> Just filter based on X-Spam-Level headers. If 8 is certainly spam then
> have your server side filter or client filter look for 8 *s, then look
> for 5 *s for probably spam. Very simple, no code changes needed.
>
> Jay
Thanks for the response, J
Tim Litwiller wrote:
this is the way I've been doing it in procmail - then I don't have to
count *'s
# ---
# Spamassassin - certainly spam
# ---
:0 H:
* ^X-Spam-Status: +(yes|no), +score=\/[^. ]*
* ? (( ${MA
ay Lee wrote:
Richard Duran wrote:
Hello,
I'm not sure if this belongs in the dev-list or not, but we have made
some minor changes to SA in order for us to allow our users to create
separate filters for mail that we consider to be "almost certainly"
spam, versus mail that is "probably" spam
Richard Duran wrote:
Hello,
I'm not sure if this belongs in the dev-list or not, but we have made
some minor changes to SA in order for us to allow our users to create
separate filters for mail that we consider to be "almost certainly"
spam, versus mail that is "probably" spam.
Just filter b
Hello,
I'm not sure if this belongs in the dev-list or not, but we have made
some minor changes to SA in order for us to allow our users to create
separate filters for mail that we consider to be "almost certainly"
spam, versus mail that is "probably" spam.
It should be noted that this code was o
