[KLUG Members] Tuning qmail

Jamie McCarthy members@kalamazoolinux.org
Thu, 12 Feb 2004 10:22:50 -0500


adam@morrison-ind.com (Adam Williams) writes:

> > > 1.) SPAMCop, support for this is built into almost all
> > > MDA/MTAs.  All it takes is a DNS query per message.  We've
> > > found this blocks almost all SPAM, and anything that comes
> > > through can be easily reported. This is Morrison's only
> > > anti-SPAM mechanism and we get almost none.
> > What false positive problems have you had with SpamCop? 
> 
> Zero.
> 
> > Have you had to whitelist any addresses?
> 
> No.

For activities like identifying terrorists or marking spam,
anecdotes are not all that helpful... it's the statistics that
matter.

SpamCop is run by bullies who think it's clever to block competing
anti-spam organizations as spammers.  Read more about them:

http://www.politechbot.com/p-04121.html
http://www.politechbot.com/p-04128.html
http://www.politechbot.com/p-04129.html
http://www.politechbot.com/p-04259.html
http://www.politechbot.com/p-04261.html
http://www.politechbot.com/p-04484.html
http://www.politechbot.com/p-04842.html

> did someone think executing hundreds of lines of perl for every
> mail message a good idea?  Just dumb.  Hello, my name is "C"!

Heh... Slashdot executes many thousands of lines of perl for every
dynamic webpage you hit, and we deliver 30 of those a second
without breaking a sweat.

My two cents is that I run SpamAssassin on my mail server and
don't have a problem, but then my mail traffic is pretty low, so
I'm not saying take my word for it.

Those of you who had a performance problem with SpamAssassin, you
are running spamd right?  According to my logs, my spamd processes
each incoming mail on my system with SpamAssassin in 0.2 to 1.0
seconds, typically.

And since so much of that is text processing and network activity
(reverse DNS lookups, DNSBL lookups), C wouldn't help a bit.
Perl's text manipulation is optimized.
-- 
  Jamie McCarthy
 http://mccarthy.vg/
  jamie@mccarthy.vg