[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.5.0.html]
Postfix stable release 3.5.0 is available. Support has ended for legacy release Postfix 3.1.
The main changes are below. See the RELEASE_NOTES file for further details.
Support for the haproxy v2 protocol. The Postfix implementation supports TCP over IPv4 and IPv6, as well as non-proxied connections; the latter are typically used for heartbeat tests.
Support to force-expire email messages. This introduces new postsuper(1) command-line options to request expiration, and additional information in mailq(1) or postqueue(1) output.
The Postfix SMTP and LMTP client support a list of nexthop destinations separated by comma or whitespace. These destinations will be tried in the specified order. Examples:
/etc/postfix/main.cf: relayhost = foo.example, bar.example default_transport = smtp:foo.example, bar.example
Incompatible changes:
Logging: Postfix daemon processes now log the from= and to= addresses in external (quoted) form in non-debug logging (info, warning, etc.). This means that when an address localpart contains spaces or other special characters, the localpart will be quoted, for example:
from=<"name with spaces"@example.com>
Specify "info_log_address_format = internal" for backwards compatibility.
Postfix now normalizes IP addresses received with XCLIENT, XFORWARD, or with the HaProxy protocol, for consistency with direct connections to Postfix. This may change the appearance of logging, and the way that check_client_access will match subnets of an IPv6 address.
You can find the updated Postfix source code at the mirrors listed at http://www.postfix.org/.