Wietse Venema wrote: > Michael Str?der: >> Quote from http://www.postfix.org/postconf.5.html#smtp_tls_policy_maps >> >> "The lookup result is a security level, followed by an optional list of >> whitespace and/or comma separated name=value attributes that override related >> main.cf settings." >> >> Does that mean that I can add any main.cf setting into the line which starts >> with 'smtp_tls_'? >> So all 'smtp_tls_foo' can be used as 'foo='? > > Here is a revolutionary idea. Is it documented? If not, then it is > not supported.
Well, I have read the docs (see quote from postfix web site above). But the statement in the docs is pretty broad/unprecise: "followed by an optional list of whitespace and/or comma separated name=value attributes that override related main.cf settings." This seems to imply that it's possible because the limited set of possible keywords is not documented. BTW: postfix 2.11.3 even seg faults when using a unknown keyword: Oct 25 16:33:37 srv1 postfix/smtp[27839]: warning: smtp_tls_policy_maps, next-hop destination "example.com": invalid attribute name: "CAfile" Oct 25 14:33:37 srv1 pdns_recursor[2944]: 1 [46459] answer to question 'mxint01.1and1.com.|A': 2 answers, 0 additional, took 3 packets, 0 throttled, 0 timeouts, 0 tcp connections, rcode=0 Oct 25 16:33:37 srv1 kernel: [427484.427118] smtp[27839]: segfault at 4 ip b772123b sp bfd7c320 error 4 in smtp[b7715000+19000] Ciao, Michael.
smime.p7s
Description: S/MIME Cryptographic Signature
