summaryrefslogtreecommitdiff
path: root/mail/exmh
diff options
context:
space:
mode:
authormartti <martti@pkgsrc.org>2009-08-31 09:37:49 +0000
committermartti <martti@pkgsrc.org>2009-08-31 09:37:49 +0000
commit9e3c47e8991468aa68b653ab9cb0babbb92d61dc (patch)
treec89bf2a7457f1ee5f065b104ddef1b8faab0b46e /mail/exmh
parent320a00f757668fef89203ba1a662ba314c421bcf (diff)
downloadpkgsrc-9e3c47e8991468aa68b653ab9cb0babbb92d61dc.tar.gz
Updated mail/postfix-current to 2.7.20090828
The stable release Postfix 2.6.5 addresses the defects described below (some already addressed with the not-announced Postfix 2.6.3 release). These defects are also addressed in the legacy releases that are still maintained: Postfix 2.5.9, 2.4.13 and 2.3.19. Do not use Postfix 2.6.4, 2.5.8, 2.4.12, 2.3.18, 2.7-20090807, and 2.7-20090807-nonprod. These contain a DNS workaround that causes more trouble than it prevents. It is removed until further notice. Defects fixed with Postfix 2.6.3, 2.5.9, 2.4.13 and 2.3.19: - The Postfix Milter client got 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. This problem was diagnosed with help from Alban Deniz. Defects fixed with Postfix 2.6.5, 2.5.9, 2.4.13 and 2.3.19: - The Postfix SMTP server would abort with an "unexpected lookup table" error when an SMTPD policy server was mis-configured in a particular way.
Diffstat (limited to 'mail/exmh')
0 files changed, 0 insertions, 0 deletions