ports/138198: [patch] port mail/postfix update to version 2.6.4

Sahil Tandon sahil at tandon.net
Sat Aug 29 03:10:08 UTC 2009


The following reply was made to PR ports/138198; it has been noted by GNATS.

From: Sahil Tandon <sahil at tandon.net>
To: bug-followup at FreeBSD.org
Cc: ohauer at gmx.de
Subject: Re: ports/138198: [patch] port mail/postfix update to version 2.6.4
Date: Fri, 28 Aug 2009 23:00:06 -0400

 I reject this patch because 2.6.4 has known bugs that have been fixed in
 2.6.5.  Please submit a patch to upgrade to 2.6.5 or give me a few days to do
 so myself (after I've had a chance to test).  See below message from Wietse
 (Postfix author) for context:
 
 ---
 
 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.
 



More information about the freebsd-ports-bugs mailing list