On Mon, 2013-11-11 at 17:24 -0800, John Hardin wrote:
> On Mon, 11 Nov 2013, Sergio Durigan Junior wrote:
> > Currently, in my .procmailrc, the first thing I do is scan for spam.
> > However, as you have noticed, this scanning also covers mailing lists
> > (and everything else). I think I will tweak my .procmailrc to do the SA
> > scanning *after* I have filtered my mailing lists.
>
> That's not what Karsten was suggesting. If you get spam via that mailing
> list you should complain to the list admin that they need to do a better
> job of filtering their inbound.
I did indeed state that filtering spam is the list operator's duty.
However, I also clearly stated that mailing lists are best left
unprocessed by SA and delivered into dedicated folders early. There is
absolutely no point in scanning these, it's just wasting resources. [1]
Same goes for bugzilla mail, cron noise, ...
If you have the chance, place lightweight and highly efficient filters
early in the chain. Filter out lists, bugzilla, and anything else that's
easy to detect. Then run heavyweight tests. It's the same philosophy as
using DNSBL tests to outright reject at SMTP level.
[1] Also, just as shown in this thread, properly handling list posts is
not trivial.
--
char *t="\10pse\0r\0dtu\0.@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; }}}
