For the record, I would agree 110% that a 2.1.8 would be in order. There have been *many* changes made since 2.1.7, and svn has been especially unstable lately. I think getting 2.2 release fever right now is likely to go about as well as the 2.0 release did (ie. immediate patches to fix a few overlooked things, and apologies / explanations that you really shouldn't run 2.2.0).
On Thu, 2006-11-02 at 02:58 +0100, [EMAIL PROTECTED] wrote: > ---------------------------------------------------------------------- > bjohnson - 02-Nov-06 02:29 > ---------------------------------------------------------------------- > As far as the 2.0 lmtp zombies, is there anyway to get the info > without > leaving high level logging on for weeks? These usually take a long > time > to appear. I have zombies on the machine right now and was hoping > that I > could get some useful information from them. > > ---------------------------------------------------------------------- > aaron - 02-Nov-06 02:58 > ---------------------------------------------------------------------- > We're probably going straight to 2.2.0, but we're having some final > last > issues with encodings on PostgreSQL. Hang tight for another week or > two, > and we'll have a stable release for you. > -- Jesse Norell - [EMAIL PROTECTED] Kentec Communications, Inc.
