Re: tests= SIZE_LIMIT_EXCEEDED ??

Hi, Karsten Bräckelmann-2 wrote: X-SpamScore: 0 tests= SIZE_LIMIT_EXCEEDED Some sw components to be ruled out: - this isn't amavisd-new doing it, at least none of the official versions; Right, that's definitely something else adding the headers, as has been pointed out

tests= SIZE_LIMIT_EXCEEDED ??

Hi, I just had a closer look at the header of an email which should have been recognized by spamassassin as spam. Waht I found was this: X-SpamScore: 0 tests= SIZE_LIMIT_EXCEEDED I have checked /usr/share/spamassassin/ for a rule which might contain a size limit, but didn't finde

Re: zero score rules still show up in 3.2.2

2.5.2) and still see zero scores from plugins displayed: Bug 5519. http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5519 guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t

Re: Mail not checked for spam in procmailrc

to see when replies and help offered on a mailing list is being ignored. Lots of luck, with whatever you still are struggling with. guenther [1] That are char class parenthesis, no grouping with alternation. With the pipe symbol in it and your intended usage, I'll refuse to call

Re: Mail not checked for spam in procmailrc

receipts. They might jump on these, otherwise...) guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: New version of iXhash plugin available

On Fri, 2007-07-06 at 20:15 +0200, Dirk Bonengel wrote: guenther schrieb: Unfortunately, the example iXhash.cf of (current) version 1.0 is rather scarce when it comes to the definitions. I'd wish for these to become as informative again as they used to be. FWIW, these verbose descriptions

Re: New version of iXhash plugin available

in place in the example cf file... guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: Mail not checked for spam in procmailrc

to filter the mail... Caveat: Didn't have a sane dose of coffee, yet. ;) guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: These are getting through SA...

for the spamminess in the second run is the URIBL_BLACK hit. Maybe an oops, maybe a misconfiguration, maybe due to not running in real time, but long after. So I'm blaming it on Amavis... (Net::DNS 0.59 here)... I don't see much evidence for this, yet. ;) guenther -- char *t=[EMAIL PROTECTED]; main

Re: 404 while getting RDJ updates?

On Thu, 2007-06-07 at 17:45 +0200, Anders Norrbring wrote: Anyone else getting 404 errors from RDJ lately? Yes, this topic came up just a few hours ago. Probably a dDOS attack. Please disable all RDJ till further notice. guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t

Re: Block a user based on content

attached or something like that? No. Usual answer... SA does not block mail. SA tags mail. It is the duty of whatever you are using that calls SA to take appropriate action. I would appreciate any hints! For starters... Are you actually scanning outgoing mail for Spam? guenther -- char

Re: Block a user based on content

for this kind of gathering logs. guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: what does the 'new' --allowupdates option to sa-update do?

: Defaults are there for a reason. Don't change a default, unless you fully understand the impact. guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: SA not firing on every email

the description of the spamc -x option above). ...guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: Sare URI ruleset

. It just means, that the description is more than 50 chars long, and thus a verbose report in the header may exceed an 80 chars limit. FWIW, this is pretty common with some translations, like German. ...guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0

Re: Adjusting the AWL value

::Autowhitelist you likely want 'man spamassassin'. :) See --remove-from-whitelist and --remove-addr-from-whitelist options. You can provide the email address alone or feed it the respective mail. HTH ...guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i

Re: Setting up a rejection limit

not to get false positives. ...guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: not deleting

but you can sort (move, delete, archive, whatever) any mails based on the SA score on your local end. ...guenther -- char *t=[EMAIL PROTECTED]; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1: (c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}