> On 22 Feb 2021, at 18:40, Joe Acquisto-j4 wrote: > On 22 Feb 2021, at 17:27, Joe Acquisto-j4 wrote: >>> >>>> Post fix version 3.4.7. with Spamassassin. While adding virus >>>> scanning (clamav) noticed during testing >>>> that any mail send from the postfix host does not get processed by >>>> spamassassin. >>>> >>>> Postfix does accept it and passes it right thorough without any >>>> indication it was passed through >>>> spamd or clamd. >>> >>> Critical issue: what mechanisms are you using to integrate >>> SpamAssassin >>> and ClamAV? >>> >>>> Wondering how I can fix that. That is, cause local mail to be >>>> scanned. >>>> >>>> Quick look at master.cf and main.cf, nothing jumped out to bite me. >>> >>> If you are using Milters, you need to set non_smtpd_milters to get >>> locally-submitted mail to be shown to them. If that's not the >>> solution >>> in your case (i.e. you're using the SMTP proxy or content_filter >>> mechanisms) you need to explain your configuration. >>> >>> -- >>> Bill Cole >> >> Thanks. Sorry for the terse post. Figured it was such an obvious >> amateur error not much was needed. >> >> Setting non_smtpd_milters did the trick for testing the virus scanner. >> I >> should have guessed that on my own. >> >> The content filter (spamassassin) is not a hot item. but the relevant >> lines >> from master.cf are: >> . . . >> smtp inet n - n - - smtpd -o >> content_filter=spamassassin > > You need an analogous configuration for the pickup service to get local > mail piped through the spamassassin service. See > http://www.postfix.org/FILTER_README.html. > > -- > Bill Cole . . .
I did not notice that adding non_smtpd_milters also caused off box (smtpd) mail to be scanned twice, before and after spamassassin. Apparently having both smtpd_milters and non_smtpd_milters specified in main.cf causes that. Initially it appeared to me that milters had to be specified main.cf. Delving somewhat deeper it now appears that to me milters can alternately be specified in master.cf? Is that correct? joe a
