Postfix has released updates for its stable version 3.10.4 and legacy versions 3.9.5, 3.8.11, and 3.7.16. These updates address various issues related to the postscreen and tlsproxy functionalities, primarily aimed at reducing process churn and improving portability. Specific bugs fixed include:
1. Postscreen Fixes:
- An ENOTSOCK error was being logged by old postscreen processes when they attempted to accept connections on inactive sockets.
- An issue where the old postscreen process maintained an exclusive lock on the postscreen_cache_map, preventing new processes from starting.
2. Tlsproxy Fixes:
- Corrections in backward compatibility for legacy tlsproxy configuration parameters, which previously disabled the tlsproxy client role.
- A bug that caused a null pointer dereference when the tlsproxy client role was disabled.
3. Process Management Enhancements:
- Postfix daemons will no longer automatically restart when certain table file modification times change, thereby reducing unnecessary process churn.
4. Portability Improvements:
- Removal of a build dependency on OpenSSL features that are being phased out.
Additionally, version 3.10.4 includes specific improvements such as the suppression of TLSRPT statistics for messages marked as "TLS-Required: no" and a correction in logging for TLS sessions involving trusted certificates.
For users looking to implement the latest fixes, the updated source code can be accessed through the mirrors available on the Postfix website.
In summary, these updates not only resolve critical bugs but also enhance the overall efficiency and reliability of Postfix's email handling capabilities. Users are encouraged to upgrade to benefit from these improvements and ensure optimal operation of their email servers
1. Postscreen Fixes:
- An ENOTSOCK error was being logged by old postscreen processes when they attempted to accept connections on inactive sockets.
- An issue where the old postscreen process maintained an exclusive lock on the postscreen_cache_map, preventing new processes from starting.
2. Tlsproxy Fixes:
- Corrections in backward compatibility for legacy tlsproxy configuration parameters, which previously disabled the tlsproxy client role.
- A bug that caused a null pointer dereference when the tlsproxy client role was disabled.
3. Process Management Enhancements:
- Postfix daemons will no longer automatically restart when certain table file modification times change, thereby reducing unnecessary process churn.
4. Portability Improvements:
- Removal of a build dependency on OpenSSL features that are being phased out.
Additionally, version 3.10.4 includes specific improvements such as the suppression of TLSRPT statistics for messages marked as "TLS-Required: no" and a correction in logging for TLS sessions involving trusted certificates.
For users looking to implement the latest fixes, the updated source code can be accessed through the mirrors available on the Postfix website.
In summary, these updates not only resolve critical bugs but also enhance the overall efficiency and reliability of Postfix's email handling capabilities. Users are encouraged to upgrade to benefit from these improvements and ensure optimal operation of their email servers
Postfix 3.10.4 and legacy releases 3.9.5, 3.8.11, 3.7.16 released
Postfix has issued multiple updates for its stable release 3.10.4 as well as for the legacy versions 3.9.5, 3.8.11, and 3.7.16. The updates resolve concerns related to postscreen and tlsproxy and aim to minimize process churn. The updates resolve problems related to the previous postscreen process, including the logging of an ENOTSOCK error, maintaining an exclusive lock, incorrect backward compatibility for legacy configuration parameters, and the dereferencing of a null pointer during the handling of tlsproxy client requests. Furthermore, the solutions minimize process churn and enhance portability.
Postfix 3.10.4 and legacy releases 3.9.5, 3.8.11, 3.7.16 released @ Linux Compatible
