> 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.
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.
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. A simple map could
look like this:
# /etc/postfix/main.cf:
smtpd_milters = hash:/etc/postfix/smtpd_milters, inet:..., {...}, ...
# /etc/postfix/smtpd_milter:
127.0.0.1 inet:127.0.0.1:10000, {...}, ...
134.255.226.249 ...
[2a05:bec0::134:255:226:249] ...
My first request was different to this. I propose this, as it is closer to
yours.
Is this possible?
Thanks
Christian
--
Erlenwiese 14, 36304 Alsfeld
T: +49 6631 78823400, F: +49 6631 78823409, M: +49 171 9905345
USt-IdNr.: DE225643613, https://www.roessner-network-solutions.com
smime.p7s
Description: S/MIME cryptographic signature
