Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-05-07 Thread Wietse Venema
Quanah Gibson-Mount: > --On Thursday, May 07, 2009 12:52 AM -0700 Bill Landry > wrote: > > > >>> Although the download link is correct, the text is wrong: > >>> > >>> Postfix 2.6.0 stable release candidate 2 I have fixed the text this morning (the hyperlinks already said RC3). Wietse

Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-05-07 Thread Quanah Gibson-Mount
--On Thursday, May 07, 2009 12:52 AM -0700 Bill Landry wrote: Although the download link is correct, the text is wrong: Postfix 2.6.0 stable release candidate 2 rather than Postfix 2.6.0 stable release candidate 3 A random sam

Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-05-07 Thread Bill Landry
Victor Duchovni wrote: > On Wed, May 06, 2009 at 03:26:50PM -0700, Quanah Gibson-Mount wrote: > >> --On Wednesday, April 29, 2009 8:40 AM -0400 Wietse Venema >> wrote: >> >>> Postfix 2.6 stable release candidate 3 is available. If this has >>> no problems, then Postfix 2.6.0 will happen soon. Th

Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-05-07 Thread Victor Duchovni
On Wed, May 06, 2009 at 03:26:50PM -0700, Quanah Gibson-Mount wrote: > --On Wednesday, April 29, 2009 8:40 AM -0400 Wietse Venema > wrote: > >> Postfix 2.6 stable release candidate 3 is available. If this has >> no problems, then Postfix 2.6.0 will happen soon. The same code is >> also available

Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-05-06 Thread Quanah Gibson-Mount
--On Wednesday, April 29, 2009 8:40 AM -0400 Wietse Venema wrote: Postfix 2.6 stable release candidate 3 is available. If this has no problems, then Postfix 2.6.0 will happen soon. The same code is also available as Postfix 2.7 experimental release 20090428. Although the download link is cor

Re: Postfix 2.6.0-RC3 and 2.7-20090428 available

2009-04-29 Thread Victor Duchovni
On Wed, Apr 29, 2009 at 08:40:12AM -0400, Wietse Venema wrote: > TLS changes since release candidate 2: > == > > The Postfix SMTP client(!) no longer tries to use the obsolete SSLv2 > protocol by default, as this may prevent the use of modern SSL > features. L