[pmg-devel] [PATCH pmg-docs v2] add support for next-hop TLS destination

[Stoiko Ivanov]

Adapt the documentation for TLS Destination policies to mention next-hop
destinations defined in the transport table. Support for this was introduced
with the fix for #1948.

Signed-off-by: Stoiko Ivanov <s.ivanov at proxmox.com>
---
v1 -> v2:
* added a paragraph break before the TLS destination policy after checking
  the rendered output. Sorry for the noise!

 pmgconfig.adoc | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/pmgconfig.adoc b/pmgconfig.adoc
index e6ebe57..7b2d1f7 100644
--- a/pmgconfig.adoc
+++ b/pmgconfig.adoc
@@ -409,10 +409,12 @@ certificate for you (`/etc/pmg/pmg-tls.pem`).
 {pmg} uses opportunistic TLS encryption by default. The SMTP transaction is
 encrypted if the 'STARTTLS' ESMTP feature is supported by the remote
 server.  Otherwise, messages are sent in the clear.
-You can set a different TLS policy per desitination domain, should you for
-example need to prevent e-mail delivery without encryption, or to work around
-a broken 'STARTTLS' ESMTP implementation. See {postfix_tls_readme} for details
-on the supported policies.
+
+You can set a different TLS policy per destination. A destination is either a
+remote domain or a next-hop destination as specified in `/etc/pmg/transport`.
+This can be used, should you need to prevent e-mail delivery without
+encryption, or to work around a broken 'STARTTLS' ESMTP implementation. See
+{postfix_tls_readme} for details on the supported policies.
 
 Enable TLS logging::
 
-- 
2.20.1