If you use amavis then you will not be able to use spamd/c. You will also loose the ability to FULLY manipulate the available headers in sa.
If you write your own scripts then you can spamd/c. You will also be able to add any sa header you want. Amavis reads the spamassassin.pm and compiles it into memory, therefor some say its as fast or faster than spamd/c. I started with amavis-new and have had to switch computers out to upgrade the OS. While doing that I changed to my own scripts. I'm happier with the memory usage now and the performance. Generaly speaking (and without supporting hard data) I've seen an increase in the system performance, decrease in cpu cycles and memory used overall as well as faster scan times of my messages. The difference could be OS related but I think its because of the switch from amavis-new to my own script with the use of spamd/c. I don't use individual settings and that might have an impact. Your best bet is to try it both ways and find what works best with your setup as system configurations will determine whats best. ----- Original Message Follows ----- From: Matt Goli <[EMAIL PROTECTED]> To: users@spamassassin.apache.org Subject: Questions on Spamassassin deployment Date: Wed, 3 Nov 2004 15:57:26 -0600 > Greetings all: > > I am looking for feedback and constructive criticism on how our > organization is looking to deploy SpamAssassin. The solution we are > looking for will only need to filter e-mail for virus and spam because > all user mailboxes are currently stored on an Exchange 2000 server. > > Here is what we would like to do: > > 1 - Have all inbound and outbound e-mail filter thru two redundant > Apple G5 Xserves running Mac OS 10.3.5 server using Postfix version > 2.0.10 as the MTA. > 2 - All e-mail will be filtered for viruses using ClamAV tied into > Postfix via Amavisd. (That part is simple) > 3 - How should SpamAssassin be tied in? I have read arguments both > ways whether or not to use spamd/spamc or use Amavisd. Spamd/spamc I > feel is more configuration, but seems to allow the use of all of > SpamAssassin's built-in features, as opposed to Amavisd being easy to > integrate with Spamassassin, but use of built-in Spamassassin features > are limited. What is everyone else's take on that? > 4 - We wish to provide per-user preferences, AWL and bayesian databases > using MySQL. For using MySQL is it better to use Amavisd or > spamd/spamc? Also, if we are going to have redundant e-mail filters, > it would make sense to provide redundant MySQL servers. Can we run > MySQL on both boxes and have SA writing back to both databases on both > servers at the same time? If SA can be writing to two different MySQL > servers at one time, can the two filter servers be in two different > data centers, i.e. one server in New York and one in San Diego? > > I think that about sums up my questions, any feedback, concerns, > questions or references are greatly appreciated. > > Thank you, > --- > Matt Goli, MCP > Systems Support Group > > F+W Publications, Inc. > - www.fwpublications.com > Krause Publications, a division of F+W Publications, Inc. > - www.krause.com > ========================= Kevin W. Gagel Network Administrator Information Technology Services (250) 561-5848 local 448 -------------------------------------------------------------- The College of New Caledonia, Visit us at http://www.cnc.bc.ca Virus scanning is done on all incoming and outgoing email. --------------------------------------------------------------
