> On Oct 18, 2017, at 12:45 AM, Viktor Dukhovni
> wrote:
>
> The documentation for the TLS policy table clearly states that the
> lookup key for the TLS policy is the *verbatim* nexthop.
http://www.postfix.org/TLS_README.html#client_tls_policy
The TLS policy
On Tue, Oct 17, 2017 at 11:03:46PM -0400, J Doe wrote:
> “The [] enclose a hostname which is to be looked up as a type A or
> record. Without the [] first a lookup of type MX is done, and
> where found, prioritized lookups of further hostnames (A or )
> would be done.
That's what
Hi Wietse,
> On Oct 11, 2017, at 7:11 PM, Wietse Venema wrote:
>
> J Doe:
>> Hi,
>>
>> I have a syntax question regarding configuring mandatory TLS encryption for
>> the smtp process as listed on: www.postfix.org/TLS_README.html#client_tls
>>
>> In the second example on
J Doe:
> Hi,
>
> I have a syntax question regarding configuring mandatory TLS encryption for
> the smtp process as listed on: www.postfix.org/TLS_README.html#client_tls
>
> In the second example on the page, square brackets are used when specifying
> the policy for specific destinations in the
On Wed, Oct 11, 2017 at 05:36:07PM -0400, J Doe wrote:
> I have a syntax question regarding configuring mandatory TLS
> encryption for the smtp process as listed on:
> www.postfix.org/TLS_README.html#client_tls
>
> In the second example on the page, square brackets are used when
> specifying
Hi,
I have a syntax question regarding configuring mandatory TLS encryption for the
smtp process as listed on: www.postfix.org/TLS_README.html#client_tls
In the second example on the page, square brackets are used when specifying the
policy for specific destinations in the tls_policy file: