Re: smtpd_milter_maps and XFORWARD

2022-04-20 Thread Wietse Venema
Jesper Dybdal: > On 2022-04-08 16:22, Wietse Venema wrote: > > Jesper Dybdal: > >> I run Amavis as a before-queue filter, and opendmarc in the after-Amavis > >> smtpd instance. > > Why not use Amavis as a before-queue MILTER? Then there is no need > > to propagate remote SMTP client info through no

Re: smtpd_milter_maps and XFORWARD

2022-04-20 Thread Jesper Dybdal
On 2022-04-08 16:22, Wietse Venema wrote: Jesper Dybdal: I run Amavis as a before-queue filter, and opendmarc in the after-Amavis smtpd instance. Why not use Amavis as a before-queue MILTER? Then there is no need to propagate remote SMTP client info through non-Postfix programs. Thanks for the

Re: smtpd_milter_maps and XFORWARD

2022-04-09 Thread Wietse Venema
Jesper Dybdal: > On 2022-04-08 20:10, Wietse Venema wrote: > > You can specify multiple Milters. Each Milter only sees the inputs > > that Postfix and earlier Milters have allowed. Message content > > changes made by one Milter are visible to Milters that follow. > > Thanks. Can milters also see c

Re: smtpd_milter_maps and XFORWARD

2022-04-09 Thread Jesper Dybdal
On 2022-04-08 20:10, Wietse Venema wrote: You can specify multiple Milters. Each Milter only sees the inputs that Postfix and earlier Milters have allowed. Message content changes made by one Milter are visible to Milters that follow. Thanks.  Can milters also see content changes (added headers

Re: smtpd_milter_maps and XFORWARD

2022-04-08 Thread Wietse Venema
Jesper Dybdal: > Are smtpd_recipient_restrictions, particularly policy services, > evaluated before milters, so that I could use policyd_spf to check SPF, > and have amavis and opendmarc milters in that same smtpd instance - so > the milters could use the Authentication-Results header from polic

Re: smtpd_milter_maps and XFORWARD

2022-04-08 Thread David Bürgin
Jesper Dybdal: > Are smtpd_recipient_restrictions, particularly policy services, evaluated > before milters, so that I could use policyd_spf to check SPF, and have > amavis and opendmarc milters in that same smtpd instance - so the milters > could use the Authentication-Results header from policyd_

Re: smtpd_milter_maps and XFORWARD

2022-04-08 Thread Jesper Dybdal
On 2022-04-08 16:22, Wietse Venema wrote: Jesper Dybdal: I run Amavis as a before-queue filter, and opendmarc in the after-Amavis smtpd instance. Why not use Amavis as a before-queue MILTER? Then there is no need to propagate remote SMTP client info through non-Postfix programs. That might we

Re: smtpd_milter_maps and XFORWARD

2022-04-08 Thread Benny Pedersen
On 2022-04-08 15:53, Jesper Dybdal wrote: I run Amavis as a before-queue filter, and opendmarc in the after-Amavis smtpd instance. I would like to use smtpd_milter_maps to exclude some networks from the DMARC check. But it does not seem to work.  My guess is that this is because the smtpd insta

Re: smtpd_milter_maps and XFORWARD

2022-04-08 Thread Wietse Venema
Jesper Dybdal: > I run Amavis as a before-queue filter, and opendmarc in the after-Amavis > smtpd instance. Why not use Amavis as a before-queue MILTER? Then there is no need to propagate remote SMTP client info through non-Postfix programs. Postfix supports XFORWARD for logging which requires a

smtpd_milter_maps and XFORWARD

2022-04-08 Thread Jesper Dybdal
I run Amavis as a before-queue filter, and opendmarc in the after-Amavis smtpd instance. I would like to use smtpd_milter_maps to exclude some networks from the DMARC check. But it does not seem to work.  My guess is that this is because the smtpd instance that should do this comes after Ama