If you have external MX boxes that are not your main mail server, through dns you can ponit the domains you want filtered to the mx hosts, and the other non-filtered domains to the main mail server.

I currently run a mail system somewhat like that and we use qmail with spamassassin combined with several dnsbl lists like the one spamcop offers (www.spamcop.net).

I would not use only spamassassin. Since it is public information, spammers use this to avoid getting caught by it. It works great for virus scanning, but it does not catch too much spam. I do have ours turned down, but you will have to do that if you are scanning mail for clients.

What do you mean 15GB mail traffic / server? Mine currently handles about 300k pieces of mail, and it's load balanced over two dual piii-733 dell power edges running debian. They run about 75% loaded all day, with a load of about 1.5. CPU speed is important, but don't forget about ram. The machines would not handle the load with 256 megs of ram (random crashing).

-Jason


Markus Welsch wrote:

hi all,

does any of you use latest version of spamassassin in your isp environment? i'm considering installing it as content-filter (Postfix 2.07 as MTA) on both mx servers ... the only thing that holds me back is how it responses to performance for 15 GB mail traffic / server. how are your experiences with it?

since it's written in perl it will be a huge performance decrease, right?


would it be possible to do filtering just for specified domains ?



greetings,

markus







Reply via email to