On Mon, 01 Apr 2019 14:57:01 -0400 Scott Kitterman <deb...@kitterman.com> wrote: > On Mon, 01 Apr 2019 14:30:04 -0400 Scott Kitterman <deb...@kitterman.com> > wrote: > > Package: release.debian.org > > Severity: normal > > Tags: stretch > > User: release.debian....@packages.debian.org > > Usertags: pu > > > > This is the next in a series. It contains upstream bug fix releases > > 3.1.10, 3.1.11, and 3.1.12. I held off after 3.1.10 since it contains > > somewhat more new/changed code than these usually do. Both 3.1.11 and > > 3.1.12 have since been released with no corrections needed to the > > refactored code. > > > > I have been running 3.1.10/11 in production for some time and currently > > have 3.1.12 in production. All with no issues. > > > > I am particularly motivated to move forward with another stable update now > > because 3.1.12 fixes an LMTP performance issue that likely has been > > hurting any high volume receivers and is a regression for oldstable -> > > stable. > > > > There are also fixes for several smtputf8 fixes that are oldstable -> > > stable regressions. > > > > Other than the openssl related refactoring that has been extensively > > tested by the postfix community, most of the changes are documentation. > > The other code changes seem reasonably compact and low risk. > > Forgot to mention in the original bug that there's also a pending unblock > request for 3.4.5-1 (#926188) that will cover getting the LMTP performance > fix into Buster.
postfix 3.4.5-1 is in Testing now, so Testing now has all the fixed proposed here for Stable. Scott K