> > Besides, is there any specific reason why you use spamd with amavis? > > 'cause we already have a spamd running. > Anyway, is there any *real* performance difference in running > spamassassin rather than spamc from amavis? > Or, better question, why should I use spamassassin instead of spamc? :)
Amavisd pre-spawns spamassassin instances the way spamd do, only a bit better... ;) Runnin SA from inside amavis, you wouldn't get any performance penalty with respect to using spamd, while you gain something in return from their mutual tighter integration. The "autolearn" message is an example of the advantages you would get. This is because amavisd uses the Mail::SpamAssassin interface to "communicate" with SA, which is a much broader and fast "channel" than the thin and simple one offered by a socket interface. Also, this is the amavis' most common usage pattern. Proof is you had to change amavis code (as opposed to the configuration file) in order to enable SA via spamd. I *guess* the interface you're using is a remnant of the first amavisd days, when most of the people was using spamd to run SA and the amavisd developers wanted to reduce any configuration impact to people willing to deploy amavisd. However, most of the configuration tutorials, examples and hints you may find in the net are about the 'stock' Mail::SpamAssassin setup. > thanks so much, > stefano You're welcome. Giampaolo ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
