Patrick Proniewski:
> Thanks Wietse,
>
> > On 01 mai 2020, at 15:37, Wietse Venema <wie...@porcupine.org> wrote:
> >
> > Patrick Proniewski:
> >> I really feel like my setup needs some cleanup and I'm not sure were to
> >> start. Some of you have suggested to me, in the past, that I could move to
> >> amavisd-milter instead of smtpd_proxy_filter for antispam/antivirus
> >> filtering. It might be the way but I don't know if it can help me with my
> >> new need.
> >
> > It may well be:
> >
> > - You can use amavisd-milter to filter inbound SMTP mail (with
> > smtpd_milters) and /usr/sbin/sendmail local submissions (with
> > non_smtpd_milters). The two settings can be different if needed.
>
> would there be a performance/functionality penalty switching from
> smtpd_proxy_filter to smtpd_milters/non_smtpd_milters?
It will be faster, because it avoids the need to deliver the whole
message outside of Postfix, and then to receive the whole message
again into Postfix.
Also, the logging will be easier to follow because there is only
one queue file instead of two (one before amavisd and one after
amavisd).
> > - Assuming that amavisd supports per-user configuration, it
> > can be told not to touch email for your fetchmail user.
> >
> > - Otherwise, maybe you can configure fetchmail to talk to a dedicated
> > smtpd entry in master.cf that has "-o smtpd_milters=". i.e. no filter.
>
> not sure about the per-user, but I can definitely do a lot of
> plumbing inside amavisd, or apparently tune fetchmail to deliver
> into a dedicated smtp.
Wietse
