Postfix Changelog

New in version 2.7.0

February 21st, 2010
  • Improved before-queue content filter performance. With "smtpd_proxy_options = speed_adjust", the Postfix SMTP server receives the entire message before it connects to a before-queue content filter. Typically, this allows Postfix to handle the same mail load with fewer content filter processes.
  • Improved address verification performance. The verify database is now persistent by default, and it is automatically cleaned periodically. Under overload conditions, the Postfix SMTP server no longer waits up to 6 seconds for an address probe to complete.
  • Support for reputation management based on the local SMTP client IP address. This is typically implemented with "FILTER transportname:" actions in access maps or header/body checks, and mail delivery transports in with unique smtp_bind_address values.
  • The postscreen daemon (a zombie-blocker in front of Postfix) is still too rough for a stable release, and will be made "mature" in the Postfix 2.8 development cycle (however you can use Postfix 2.7 with the Postfix 2.8 postscreen and dnsblog executables and configuration; this code has already proven itself).

New in version 2.6.5 (August 31st, 2009)

  • The Postfix Milter client would be out of step with a Milter application after the application sent a "quarantine" request at end-of-message time.
  • The Milter application would still be in the end-of-message state, while Postfix would already be working on the next SMTP event, typically QUIT or MAIL FROM.
  • In the latter case, Milter responses for the previously-received email message would be applied towards the next MAIL FROM transaction.
  • The Postfix SMTP server would abort with an "unexpected lookup table" error when an SMTPD policy server was mis-configured in a particular way.

New in version 2.5.6 (January 5th, 2009)

  • The SMTP server did not ask for a client certificate with "smtpd_tls_req_ccert = yes".
  • Reduced TCP performance is avoided when reusing an SMTP connection with a larger than 4096-byte TCP MSS value.