You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
PowerMTA 5.0r6
- Thread starter Planeti
- Start date
likeeee
there is a newer version ...
do you have it ?
2020-10-27: released build 5.0r6
– added support for SMTP MTA Strict Transport Security (MTA-STS) mechanism, described
in RFC 8461, for enforcing secure delivery of email over encrypted connections
to remote domains that support it;
– added support for persistent connections for inbound HTTP connections when using
Transmissions API to submit messages to PowerMTA;
– greatly improved speed of reload operation when configuration file has large number
of domain keys and virtual MTAs defined;
– disallowed TLSv1.1 by default for incoming SMTP and HTTP connections to PowerMTA since
it is now considered deprecated;
– added support for HAProxy protocol version 2 for outbound traffic from PowerMTA;
– fixed bugs in webhooks delivery when using compressed delivery over HTTPS and reduced
frequency of retries when webhook connection attempts fail;
– added List-Unsubscribe-Post to the default list of headers that are included in
DKIM signature;
– upgraded to OpenSSL 1.1.1g, to get the latest bug fixes;
– other small improvements and fixes;
2020-07-13: released build 5.0r5
– added support for volume based licensing option in PowerMTA; contact PowerMTA sales
for more details about the new volume licensing option;
– added support for writing accounting files in JSON format in addition to regular CSV
format;
– added support for webhooks to deliver accounting data in CSV or JSON format over
HTTP(S) to a remote server; see User’s Guide for more details on how to configure
webhooks for accounting files;
– added support for customizing with interpolation of select variables in “From” & “Subject”
headers and content of the body of DSN reports issued by PowerMTA;
– restructured the User’s Guide to highlight the various SMTP & HTTP APIs available
with PowerMTA, and specifically added more detailed documentation on HTTP APIs;
– fixed crash caused when processing email addresses with malformed UTF-8 characters
during inbound reception;
– fixed source IP address for a connection incorrectly shown as “255.255.255.255”
in some circumstances in “Errors” column on the web monitor’s queue detail page;
– fixed PMTA SNMP daemon failing to start in AgentX subagent mode;
– we have added a retrospective entry to the 5.0r2 changelog reproduced here;
fixed proxy connection information not being cleared before reusing a connection worker
in another queue. Only affects PowerMTA 5.0r1 version when using proxy feature;
we recommend upgrading to at least PowerMTA 5.0r2 version if you use proxy feature;
2021-01-07: released build 5.0r7
– added support to configure click tracking and top/bottom open pixel insertions independently
from each other when using engagement tracking with SparkPost Signals;
– extended “smtp-pattern-list” to allow specifying the time interval after which a queue will
return to normal mode after being set into backoff mode with the mode=backoff action;
– extended “include” directive to support fetching configuration from external sources
through HTTP or HTTPS;
– added support for DKIM signing DSN emails issued by PowerMTA;
– added “pmta show vmta-settings” command to view settings of a particular VirtualMTA;
– added support for customizing key length of DH (Diffie-Hellman) parameters used during a
TLS 1.1 or TLS 1.2 handshake;
– added “max-memory-usage-percent” directive to configure the maximum memory consumption
of the PowerMTA process beyond which it will stop accepting incoming email;
– fixed a bug in cold VirtualMTA selection which reduced the amount of email rerouted to
a cold virtual MTA when MX rollup patterns are also configured;
– upgraded to OpenSSL 1.1.1i, to get the latest bug fixes;
– other small improvements and fixes;
PowerMTA Enterprise 5.0r8 - PowerMTA 5.0r8
2021-04-28: released build 5.0r8
– extended domain-key directive to support using keys stored in HashiCorp Vault for
DKIM signing;
– added support for adding recipient metadata and tags from X-MSYS-API header to Signals
ingest data;
– introduced a new directive – smtp-proxy-source-host – to support the use of multiple,
possibly independent, proxy servers from within a single virtual MTA;
– added additional connection-related information to accounting files when delivering email
through a proxy server;
– optimized check for expired messages in a queue containing recipients with a delivery
schedule;
– upgraded to OpenSSL 1.1.1k, to get the latest bug fixes;
– upgraded to PCRE 8.44, to get the latest bug fixes;
– other small improvements and fixes;
do you have it ?
Post automatically merged:
2020-10-27: released build 5.0r6
– added support for SMTP MTA Strict Transport Security (MTA-STS) mechanism, described
in RFC 8461, for enforcing secure delivery of email over encrypted connections
to remote domains that support it;
– added support for persistent connections for inbound HTTP connections when using
Transmissions API to submit messages to PowerMTA;
– greatly improved speed of reload operation when configuration file has large number
of domain keys and virtual MTAs defined;
– disallowed TLSv1.1 by default for incoming SMTP and HTTP connections to PowerMTA since
it is now considered deprecated;
– added support for HAProxy protocol version 2 for outbound traffic from PowerMTA;
– fixed bugs in webhooks delivery when using compressed delivery over HTTPS and reduced
frequency of retries when webhook connection attempts fail;
– added List-Unsubscribe-Post to the default list of headers that are included in
DKIM signature;
– upgraded to OpenSSL 1.1.1g, to get the latest bug fixes;
– other small improvements and fixes;
2020-07-13: released build 5.0r5
– added support for volume based licensing option in PowerMTA; contact PowerMTA sales
for more details about the new volume licensing option;
– added support for writing accounting files in JSON format in addition to regular CSV
format;
– added support for webhooks to deliver accounting data in CSV or JSON format over
HTTP(S) to a remote server; see User’s Guide for more details on how to configure
webhooks for accounting files;
– added support for customizing with interpolation of select variables in “From” & “Subject”
headers and content of the body of DSN reports issued by PowerMTA;
– restructured the User’s Guide to highlight the various SMTP & HTTP APIs available
with PowerMTA, and specifically added more detailed documentation on HTTP APIs;
– fixed crash caused when processing email addresses with malformed UTF-8 characters
during inbound reception;
– fixed source IP address for a connection incorrectly shown as “255.255.255.255”
in some circumstances in “Errors” column on the web monitor’s queue detail page;
– fixed PMTA SNMP daemon failing to start in AgentX subagent mode;
– we have added a retrospective entry to the 5.0r2 changelog reproduced here;
fixed proxy connection information not being cleared before reusing a connection worker
in another queue. Only affects PowerMTA 5.0r1 version when using proxy feature;
we recommend upgrading to at least PowerMTA 5.0r2 version if you use proxy feature;
Post automatically merged:
2021-01-07: released build 5.0r7
– added support to configure click tracking and top/bottom open pixel insertions independently
from each other when using engagement tracking with SparkPost Signals;
– extended “smtp-pattern-list” to allow specifying the time interval after which a queue will
return to normal mode after being set into backoff mode with the mode=backoff action;
– extended “include” directive to support fetching configuration from external sources
through HTTP or HTTPS;
– added support for DKIM signing DSN emails issued by PowerMTA;
– added “pmta show vmta-settings” command to view settings of a particular VirtualMTA;
– added support for customizing key length of DH (Diffie-Hellman) parameters used during a
TLS 1.1 or TLS 1.2 handshake;
– added “max-memory-usage-percent” directive to configure the maximum memory consumption
of the PowerMTA process beyond which it will stop accepting incoming email;
– fixed a bug in cold VirtualMTA selection which reduced the amount of email rerouted to
a cold virtual MTA when MX rollup patterns are also configured;
– upgraded to OpenSSL 1.1.1i, to get the latest bug fixes;
– other small improvements and fixes;
Post automatically merged:
PowerMTA Enterprise 5.0r8 - PowerMTA 5.0r8
2021-04-28: released build 5.0r8
– extended domain-key directive to support using keys stored in HashiCorp Vault for
DKIM signing;
– added support for adding recipient metadata and tags from X-MSYS-API header to Signals
ingest data;
– introduced a new directive – smtp-proxy-source-host – to support the use of multiple,
possibly independent, proxy servers from within a single virtual MTA;
– added additional connection-related information to accounting files when delivering email
through a proxy server;
– optimized check for expired messages in a queue containing recipients with a delivery
schedule;
– upgraded to OpenSSL 1.1.1k, to get the latest bug fixes;
– upgraded to PCRE 8.44, to get the latest bug fixes;
– other small improvements and fixes;
Last edited:
I think only a small group of people here know how pricless this is. Thanks!