> I'm giving some though to deploying the Vbounce ruleset into an existing
> SA 3.1.9+Maia Mailguard / 5,000 user email environment. It makes good
> sense; the only thing that seems off is the scoring. As I see it, none
> of the rules score greater then 0.1. It's hard to see how that's going
> to catch much of any spam -- even if BOUNCE_MESSAGE, CRBOUNCE_MESSAGE,
> and VBOUNCE_MESSAGE all hit together it wouldn't score more then 0.3.
VBounce is not intended to flag bounces as spam. It's purpose is to
identify and catch bounces. Please check the recent archives for threads
about the VBounce plugin or backscatter.
Now, here goes my favorite quote these days, *yet* again:
$ grep -A 2 procmail /usr/share/spamassassin/20_vbounce.cf
# If you use this, set up procmail or your mail app to spot the
# "ANY_BOUNCE_MESSAGE" rule hits in the X-Spam-Status line, and move
# messages that match that to a 'vbounce' folder.
> My question is to people who've been using the rules in a real
> production environment -- do you see them working with the default
> scores, or have you tweaked them at all?
Justin, maybe the documentation should clearly state the source code
comment above. Unfortunately, that part is missing from the docs, and
only mentioned in the rules file itself.
Given how often I have repeated that snippet over and over again, I
wonder if folks even read related posts before asking... *sigh*
guenther
--
char *t="[EMAIL PROTECTED]";
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; }}}
