Marek Kozlowski wrote:
:-)
I know that clamav and spamassassin are out of scope of this list. But
my question is more postfix-related. Most systems and Linux distros have
tutorials on postfix, spamassassin and clamav. In most of I've read the
recommended way of connecting clamav is via smtpd_milters in main.cf.
But spamassassin in those tutorial is not connected that way but a
master.cf entry is defined and a "-o content_filter=that_entry" for smtp
service is added. If so many people do that there must be some reason
for it. I'm wondering: what is the reason? what's the difference?
I would say the main reason for the difference is that the core
SpamAssassin project itself doesn't have a milter component, so there's
no way to use that method to link it in, whereas ClamAV doesn't really
have a content-filter-compatible mode that I recall where it can pass
through complete messages with optional flagging - but it does natively
include a milter component.
Personally I'd rather call both from a secondary glue layer for more
flexibility (especially for certain ClamAV tests that are valuable but
which I don't trust as absolute go/no-go results). My own favoured tool
is MIMEDefang since it can express complex filtering policies based on
results from multiple tools like SpamAssassin or ClamAV plus anything
you can code up in Perl. For inbound mail I prefer to push SpamAssassin
out to the final delivery for more flexible per-user handling as well as
integrating it with mail sorting.
-kgd