Christian Ro??ner:
>
> > Am 25.10.2016 um 08:22 schrieb Wietse Venema <wie...@porcupine.org>:
> >
> > Wietse Venema:
> >> Wietse Venema:
> >>> Looks like either 1) an exclusion mechanism or 2) a selection
> >>> mechanism would do the job.
> >>>
> >>> 1) Nullifies the smtpd_milters setting depending on the client.
> >>>
> >>> 2) Chooses the smtpd_milters setting depending on the client.
> >>>
> >>> I'll think about it.
> >>
> >> I've implemented the second variant. If you maintain configurations
> >> by hand, then excluding mynetworks will be a bit of extra work. I
> >> recommend that configurations aren't maintained by hand.
> >
> > Listed on ftp.porcupine.org/mirrors/postfix-release/index.html as
> > postfix-3.2-20161024-nonprod.
>
> I just compiled this version. I give it a try.
It needs one change, otherwise it segfaults without smtpd_milter_maps
setting. I'll push out an update later today.
> Currently I am not sure how to use this feature for my problem,
> as it does not really address my asked request. It is a boolean
> all-or-nothing setting. So now I turn off all milters for a
> system,... not exactly what I hoped.
Please RTFM. It is NOT all or nothing.
> Maybe there was another solution: Giving smtpd_milters the possibility
> to ask a map. This way, I can use LDAP to serve the right milters.
That's how the smtpd_milter_maps feature already works.
Wietse
