Postfix stable release 2.8.1 available
[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-2.8.1.html] Postfix stable release 2.8.1 is available. This release fixes one "signal 11" bug with SMTP server debug logging, and cleans up some code and documentation. - Fixed a "signal 11" bug with Postfix SMTP server debug logging at smtpd_tls_loglevel >= 3. - The Postfix SMTP and QMQP servers no longer look up IPv6 address information while looking up the FCRDNS (forward-confirmed reverse DNS) hostname for an IPv4 remote client (and vice versa). - The postscreen(8) daemon no longer logs a "connection reset by peer" warning when a remote SMTP client hangs up prematurely. - Removed spurious configuration parameters from "postconf" output, by deleting the #ifdef MIGRATION_WARNING transitional code from postscreen(8). - Assorted minor documentation fixes. You can find Postfix version 2.8.1 at the mirrors listed at http://www.postfix.org/ Wietse
Re: Postfix stable release 2.8.1 available
Hi, > Postfix stable release 2.8.1 is available. This release fixes one > "signal 11" bug with SMTP server debug logging, and cleans up some > code and documentation. Ubuntu packages done. https://launchpad.net/~christian-roessner-net/+archive/ppa - I dropped HP-UX patches from Debain, as they are useless in Ubuntu - I dropped chroot environment, as discussed lately on this list Christian -- Roessner-Network-Solutions Bachelor of Science Informatik Nahrungsberg 81, 35390 Gießen F: +49 641 5879091, M: +49 176 93118939 USt-IdNr.: DE225643613 http://www.roessner-network-solutions.com
Re: Postfix stable release 2.8.1 available
On Wednesday, February 23, 2011 09:02:09 am Christian Roessner wrote: > Hi, > > > Postfix stable release 2.8.1 is available. This release fixes one > > "signal 11" bug with SMTP server debug logging, and cleans up some > > code and documentation. > > Ubuntu packages done. > > https://launchpad.net/~christian-roessner-net/+archive/ppa > > - I dropped HP-UX patches from Debain, as they are useless in Ubuntu > - I dropped chroot environment, as discussed lately on this list What to do about chrooting by default is a conversation we should have at the distro level. I know it's a long standing disagreement between upstream and the Debian/Ubuntu maintainer, but this isn't the place to resolve it. Scott K
Re: Postfix stable release 2.8.1 available
Hi, > > - I dropped HP-UX patches from Debain, as they are useless in Ubuntu > > - I dropped chroot environment, as discussed lately on this list > > What to do about chrooting by default is a conversation we should have at the > distro level. I know it's a long standing disagreement between upstream and > the Debian/Ubuntu maintainer, but this isn't the place to resolve it. Excuse me, but you took different packages for Ubuntu and my PPA is a backport or even does not exist in current Ubuntu releases. Removing chroot does even not hurt anybody, because existing configurations won't be touched by the distro and newly installed instances do not have disadvantages. I have not modified the init script, so people still can do chrooting and the init script will work as always. Regards Christian -- Roessner-Network-Solutions Bachelor of Science Informatik Nahrungsberg 81, 35390 Gießen F: +49 641 5879091, M: +49 176 93118939 USt-IdNr.: DE225643613 http://www.roessner-network-solutions.com
Re: Postfix stable release 2.8.1 available
On Wednesday, February 23, 2011 09:33:35 am Christian Roessner wrote: > Hi, > > > > - I dropped HP-UX patches from Debain, as they are useless in Ubuntu > > > - I dropped chroot environment, as discussed lately on this list > > > > What to do about chrooting by default is a conversation we should have at > > the distro level. I know it's a long standing disagreement between > > upstream and the Debian/Ubuntu maintainer, but this isn't the place to > > resolve it. > > Excuse me, but you took different packages for Ubuntu and my PPA is a > backport or even does not exist in current Ubuntu releases. > > Removing chroot does even not hurt anybody, because existing > configurations won't be touched by the distro and newly installed > instances do not have disadvantages. > > I have not modified the init script, so people still can do chrooting > and the init script will work as always. I didn't take anything. The primary maintainer of the package uploaded 2.8.0 much as he always does. As I said before, this isn't the place to discuss it. This is my last comment on this thread. Scott K
Re: Postfix stable release 2.8.1 available
Hi, > > I have not modified the init script, so people still can do chrooting > > and the init script will work as always. > > I didn't take anything. The primary maintainer of the package uploaded 2.8.0 > much as he always does. As I said before, this isn't the place to discuss > it. > This is my last comment on this thread. your answer overlapped my last personal answer to you. Never mind Christian -- Roessner-Network-Solutions Bachelor of Science Informatik Nahrungsberg 81, 35390 Gießen F: +49 641 5879091, M: +49 176 93118939 USt-IdNr.: DE225643613 http://www.roessner-network-solutions.com
Re: Postfix stable release 2.8.1 available
On 02/23/2011 03:02 PM, Christian Roessner wrote: Hi, Postfix stable release 2.8.1 is available. This release fixes one "signal 11" bug with SMTP server debug logging, and cleans up some code and documentation. Ubuntu packages done. https://launchpad.net/~christian-roessner-net/+archive/ppa - I dropped HP-UX patches from Debain, as they are useless in Ubuntu - I dropped chroot environment, as discussed lately on this list Christian I upgraded to these packages, thanks for that. However, I was hoping the fixes mentioned by Wietse would also get rid of the incessant "postfix/postscreen[25978]: warning: getpeername: Transport endpoint is not connected -- dropping this connection" messages in my logs. I suppose postscreen is saying the client went bye-bye without saying bye-bye, but this happens more often than there are actual delivery attempts! It could be valuable for troubleshooting, but for day-to-day usage - I don't care. -- J.
Re: Postfix stable release 2.8.1 available
Jeroen Geilman: > I upgraded to these packages, thanks for that. > > However, I was hoping the fixes mentioned by Wietse would also get rid > of the incessant "postfix/postscreen[25978]: warning: getpeername: > Transport endpoint is not connected -- dropping this connection" > messages in my logs. I can't fix a "problem" that no-one tells me about. > I suppose postscreen is saying the client went bye-bye without saying > bye-bye, but this happens more often than there are actual delivery > attempts! Perhaps the problem is that you have a bad router, or a kernel with a weird implementation of accept(2). For example, early Linux accept() implementations would actually wake up as soon as the first SYN arrived, resulting in all kinds of WTF errors when someone tried to use the socket. People keep trying to "improve" software all the time. > It could be valuable for troubleshooting, but for day-to-day usage - I > don't care. Maybe there is a real problem. Wietse
Re: Postfix stable release 2.8.1 available
On 02/25/2011 08:58 PM, Wietse Venema wrote: Jeroen Geilman: I upgraded to these packages, thanks for that. However, I was hoping the fixes mentioned by Wietse would also get rid of the incessant "postfix/postscreen[25978]: warning: getpeername: Transport endpoint is not connected -- dropping this connection" messages in my logs. I can't fix a "problem" that no-one tells me about. I suppose postscreen is saying the client went bye-bye without saying bye-bye, but this happens more often than there are actual delivery attempts! Perhaps the problem is that you have a bad router, or a kernel with a weird implementation of accept(2). For example, early Linux accept() implementations would actually wake up as soon as the first SYN arrived, resulting in all kinds of WTF errors when someone tried to use the socket. People keep trying to "improve" software all the time. It could be valuable for troubleshooting, but for day-to-day usage - I don't care. Maybe there is a real problem. Wietse My head is hanging in shame. It's caused by a remote SMTP "alive" check I do myself - connect, then drop. -- J.
