mirror of
https://git.proxmox.com/git/pmg-docs
synced 2025-06-03 06:06:02 +00:00
add support for next-hop TLS destination
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@proxmox.com>
This commit is contained in:
parent
c68d1d8a2c
commit
91d501f67a
@ -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::
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user