On Tue, 2009-06-30 at 18:36 -0600, LuKreme wrote:
> On 30-Jun-2009, at 14:57, John Horne wrote:
> > I am currently reconfiguring SA, and have set report_safe to 0. Our
> > 'required' score is 8, and I have also configured:
>
> Raising the required score is clearly a mistake. Setting report safe
> to 0 is generally user-hostile. Setting it to one is the best option
> because it is the least destructive. The original message is
> completely untouched and can be easily recovered.
I don't necessarily agree. It might depend on the users. It's just a
safe (sic) default.
I once (long ago) had a hack to always have the wrapped original mail
displayed inline, rather than attached. Think "expanded by default".
Cause it made reviewing easier. Long ago I switched to report_safe 0,
cause it makes reviewing even easier. ;) The difference being nothing
way down to scroll to...
Yes, that *might* result in images being loaded off the net auto-
matically, depending on your MUA settings. Hence the "safe". But it
really makes reviewing harder, having the user scroll and klick each
single spam.
Recovering from report_safe 0 is a piece of cake, too. Just get rid of
the X-Spam headers. Done. What's destructive about that?
--
char *t="\10pse\0r\0dtu...@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; }}}
