|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Gary V (mr88talent
hotmail.com)
Date: Tue Jul 03 2007 - 10:35:44 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>Howdy!
>
>Putting together a presentation on a new mail system for some executives--
>namely, lots of graphs, powerpoint slides, and shiny clipart.
>
>Does anyone have any anecdotal data on how much overhead amavisd-new
>(SpamAssassin and ClamAV) and postfix use as opposed to filtering mail
>after it's been accepted (currently done through MailScanner)?
>
>Sorry if this is vague, I can do my best to clarify if need be.
Amavisd-new/spamassassin should be used as an after queue filter (just as
you are now running MailScanner). Use as an smtp proxy server is not
recommended for a busy server. In can sometimes be used without issue on a
high powered low volume server and there are obvious advantages to doing so,
but on a high volume server the problems will immediately become apparent.
The load SpamAssassin places on resources is significant. You would need a
large number of amavisd-new processes running in order to keep up with mail
traffic coming in the front door which would create a substantial burden.
This situation would require a very powerful server. It's better to use
other cheaper methods to trim down as much spam as practical at the front
door and feed the remaining to amavisd-new.
Gary V
_________________________________________________________________
http://newlivehotmail.com
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]