We have been using SpamAssassin (SA) for a very long time and we find it very effective in purging spam. Make sure these filters are also installed and configured properly: Razor-agents (although a little out-date), DCC, SPF, and Pyzor.Is there any better (paid/free) spam filters which can easily be added into the Exim setup?
MailScanner (MS) is not tied to any particular virus scanner, but can be used with any combination of about 14 different virus scanners. MS is the resource hog and that's one of the reasons we'll put it at the end of our list. For more information about MS, go to: http://www.mailscanner.info/Isn't MailScanner just a more efficient way of running SpamAssassin?
I think you meant MailScanner is 'a CPU hog'.Be warned though, SpamAssassin is a CPU hog
Check out ASSP it is way better. and FreeIs there any better (paid/free) spam filters which can easily be added into the Exim setup?
I havn't found spamassassin to be a problem on any of my machines.
if you have that many piling up, then it's for one (or more) of a number of reasons:Chirpy, so what installation do you recommend? I do have SA rules that are becoming big by the day. My main problem is that at any time I have like 1800 queued messages on Exim. If the messages that are sent to non-existent email IDs are set to ":fail:" and the rest are being caught by SA, then why are they queued up? Would ASSP or MailScanner help in clearing my queue?
ahhh.. these types of bounces are caused by spammers sending mail from their own servers, but listing "FROM" as an email address @YOURDOMAIN.Thanks freedman, very informative! I think for me it may be a combination of those, but no.3 is the most common. This is because the email address I have for one of my domains keeps getting spam that is like something has bounced (which it could not have, because I never sent those emails). To counter this, in my Exim config, I checked the "Exim Verify the existence of email senders" but it hasn't helped at all. What can I do to stop these bounces, or make sure that these fake emails are killed but the email address remains intact?
OK OK I retreat in defeatThat's interesting. How can you prove that 'SpamAssassin is a CPU hog'? Did you use any tool(s) to reach that conclusion? If yes, what are they? When we talk about 'CPU hog', what is the projected CPU load SA will exert on the server?
As Chirpy said, it doesn't have to be. Our setup has Exim blocking a large percentage of spam before either SA or ClamAV even touches it. It's made all the difference in the world and allowed us to run Mailscanner (and have all those great features) with no problems.I can only say empirically that SA appears to be a resource hog. In fact, if I'm to be entirely accurate with what I've observed I'd have to say that I've observed that MS/SA combined is a hog
about 70% of our spam is blocked by RBL's upon connection:As Chirpy said, it doesn't have to be. Our setup has Exim blocking a large percentage of spam before either SA or ClamAV even touches it. It's made all the difference in the world and allowed us to run Mailscanner (and have all those great features) with no problems.
Thanks, I should have mentioned what we use as standard set up. Exim with ACLs for Host/Helo checks, RBL checks, Chirpy's Dictionary attack rules, faked sender checks, message size and date checks, plus a couple of custom rules for backscatter and some other common tricks. With Exim handling these pre-anything scanning it the loads stay extremely small.about 70% of our spam is blocked by RBL's upon connection:
here are a few to consider:
check each ones site, .. some of them have more targeted lists which may be more suitable for your environment.
|Thread starter||Similar threads||Forum||Replies||Date|
|F||Antispam with API CALLS||Developer Experience||1|
|R||Looking for a better way to track forwards||Developer Experience||6|
|Can I link to auto-login WHM and go to "list accounts" page? (with search even better)||Developer Experience||4|
|A||which search platform is better||Developer Experience||0|
|S||Better Error Log: Source Code||Developer Experience||23|