[pmg-devel] [PATCH pmg-api/pmg-gui] expand TLS Destination Policy

[Stoiko Ivanov]

The following patchset addresses #1948, and allows users to specify next-hop
destinations (as defined in the transports (5) table) in additions to domains
in the tls_policy table. This is needed if you want to set a specific TLS
policy for a downstream server (from PMG's perspective) - e.g. if you need
to ensure encrypted communication with your mailserver (or if your mailservers'
TLS implementation is a broken or outdated and you need to disable TLS for it)

The minimal fix is contained in the first patch for pmg-api.

The remaining patches rename the used 'domain' property into 'destination',
since it's more fitting. I tried to maintain backward compatibility on the API
level - but would be grateful for suggestions of alternatives.


pmg-api:
Stoiko Ivanov (2):
  fix #1948: allow setting TLS policy for transports
  TLSPolicy: rename domain to destination

 src/PMG/API2/DestinationTLSPolicy.pm | 82 +++++++++++++++++-----------
 src/PMG/Config.pm                    | 34 +++++++++---
 2 files changed, 77 insertions(+), 39 deletions(-)

pmg-gui:
Stoiko Ivanov (2):
  TLSDomains: rename domain to destination
  rename TLSDomain to TLSDestination

 ...Domains.js => MailProxyTLSDestinations.js} | 32 +++++++++----------
 js/MailProxyTLSPanel.js                       |  8 ++---
 js/Makefile                                   |  2 +-
 3 files changed, 21 insertions(+), 21 deletions(-)
 rename js/{MailProxyTLSDomains.js => MailProxyTLSDestinations.js} (81%)

-- 
2.20.1