Nokin Jérôme a écrit :
> Hello,
>
> I'm currently using Postfix + Spamassassin at my office.
>
> So my master.cf file look like this :
>
> #---------------------------------------------------
> smtp inet n - n - - smtpd -o
> content_filter=
> spamassassin
> ....
> ....
> spamassassin
> unix - n n - - pipe user=nobody
> argv=/u
> sr/bin/spamc -u spamd -p 1787 -f -e /usr/sbin/sendmail -oi -f ${sender}
> ${recipi
> ent}
> #---------------------------------------------------
>
>
> Now, I would like to intergrate amavis for virus scanning.
> Because I've already tunned my spamassassin (and spend some time on it), I
> don't
> want to change my setup for migrate spamassassin from postfix to amavis.
amavisd-new uses SA config directly. so you don't need to change
anything. one exception is the Bayes data. since you used -u spamd,
you'll need to run amavisd-new as spamd to use old Bayes data.
alternatively, "convert" your Bayes data to use another user if you (want).
>
> My question is :
> There is a performance/security difference between these two architectures :
>
> 1) Postfix speak directly to spamassassin AND NEXT to amavis
This is a bit useless. if your AV is clamav, there is an SA plugin.
>
> 2) Postfix speak only to amavis which speak to spamassassin and the avscan
>
amavisd-new doesn't speak _to_ SA. It integrates SA code directly (it is
a sort of spamd over smtp/lmtp).
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
