Marc Perkel wrote:
OK - it's interesting that of all of you who responded this is the
only person who is doing it right. I have to say that I'm somewhat
surprised that so few people are preprocessing their email to reduce
the SA load. As we all know SA is very processor and memory expensive.
Personally, I'm filtering 1600 domains and I route less than 1% of
incoming email through SA. SA does do a good job on the remaining 1%
that I can't figure out with blacklists and whitelists and Exim
tricks, but if I ran everything through SA I'd have to have a rack of
dedicated SA servers.
[EMAIL PROTECTED] wrote:
Am Donnerstag, 16. August 2007 schrieb Marc Perkel:
As opposed to preprocessing before using SA to reduce the load. (ie.
using blacklist and whitelist before SA)
I use:
At rcpt time:
callout to recipient
zen.spamhaus.org <- Catches 90%
bl.spamcop.net
list.dsbl.org
callout to sender
At data time:
clamd (malware is rejected)
spamassassin (>10 Rejected, <10 add headers)
I think i will lower the spamassassin scores to 8 in the near future.
At the moment less then 5% spam reaches spamassasin.
I had great results from grey-listing but my users didn't like
having to wait 30-60-90 minutes for mail, and I understand that. When
you're on the phone with someone and they say "Just sent it," they
expect you to have it in a matter of seconds. As I'm often in that
positition, I had to support that view and remove the grey-list. I've
tried aboslute RBL blocking, but I'm happier having RBL as a weighted
factor counting for or against the spamminess of an email. We only
process about 5,000 non-spam messages per day (out of about 45,000/day
total) and are doing OK on a couple of old dual-processor systems
running it through clamd and spamd with sendmail.
