On 10.02.21 11:55, 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?
the difference between content_filter and milter is that milter runs during
SMTP session, while content_filter after mail is received.
Thus, you can reject mail with milter, so the sender has to handle it, while
rejecting in content_filter means you have to handle it.
The difference between main.cf and master.cf is that main.cf applies for
all (unless overridden), while master.cf overrides
I guess clamav scanning is faster than spamassassin scanning, so admins may
consider it more safe.
I remember that when filtering mail with milter at SMTP level, customers
complained about long time needed to send the mail.
Thus, I switched to content_filter when receiving mail from end-users
- usually services submission/587 submissions(smtps)/465,
while using milter when receiving mail from the world (port 25).
Few places where users send mail on port 25 but run server behing NAT, I ask
to NAT 25 from the world to other port where I run postscreen and milters.
Note that I usually run amavis which calls both spamassassin and clamav.
Either as content_filter, or via amavisd-milter.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Windows 2000: 640 MB ought to be enough for anybody
