-------- Original Message -------- Asunto: sendmail 8.11.5 available Fecha: Tue, 31 Jul 2001 16:54:25 -0700 De: Gregory Neil Shapiro <[EMAIL PROTECTED]> Para: [EMAIL PROTECTED] -----BEGIN PGP SIGNED MESSAGE----- Sendmail, Inc., and the Sendmail Consortium announce the availability of sendmail 8.11.5. 8.11.5 fixes bugs found since the release of 8.11.4: + A timing problem sometimes caused problems restarting the daemon with SIGHUP + Better support for wildcard IPv6 sockets (which can accept IPv4 connections) + Portability fixes for BSD/OS + Other minor bug fixes 8.11.5 is planned to be the final 8.11 release before 8.12.0 is released. Please send bug reports to [EMAIL PROTECTED] and general feedback to [EMAIL PROTECTED] It can be found at: ftp://ftp.sendmail.org/pub/sendmail/sendmail.8.11.5.tar.gz ftp://ftp.sendmail.org/pub/sendmail/sendmail.8.11.5.tar.Z ftp://ftp.sendmail.org/pub/sendmail/sendmail.8.11.5.tar.sig with MD5 signatures: 7b8c5771e5e80799c94292ff6429b7ce sendmail.8.11.5.tar.gz a296cd37d6ace601bb668005e664819c sendmail.8.11.5.tar.Z b6d3d9592d530f6db019b8c14d57d879 sendmail.8.11.5.tar.sig You need either the gzip'ed version (.gz) or the compressed version (.Z). The .sig file contains the PGP signature of the tar files (after uncompressing). The PGP signature was created using the Sendmail Signing Key/2001, available on the web site (http://www.sendmail.org/) or on the public key servers. Since sendmail 8.11 and later includes hooks to cryptography, the following information from OpenSSL applies to sendmail as well. PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS ARE NOT LIABLE FOR ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY. 8.11.5/8.11.5 2001/07/31 Fix a possible race condition when sending a HUP signal to restart the daemon. This could terminate the current process without starting a new daemon. Problem reported by Wolfgang Breyha of SE Netway Communications. Only apply MaxHeadersLength when receiving a message via SMTP or the command line. Problem noted by Andrey J. Melnikoff. When finding the system's local hostname on an IPv6-enabled system which doesn't have any IPv6 interface addresses, fall back to looking up only IPv4 addresses. Problem noted by Tim Bosserman of EarthLink. When commands were being rejected due to check_relay or TCP Wrappers, the ETRN command was not giving a response. Incoming IPv4 connections on a Family=inet6 daemon (using IPv4-mapped addresses) were incorrectly labeled as "may be forged". Problem noted by Per SteinarIversen of Oslo University College. Shutdown address test mode cleanly on SIGTERM. Problem noted by Greg King of the OAO Corporation. Restore the original real uid (changed in main() to prevent out of band signals) before invoking a delivery agent. Some delivery agents use this for the "From " envelope "header". Problem noted by Leslie Carroll of the University at Albany. Mark closed file descriptors properly to avoid reuse. Problem noted by Jeff Bronson of J.D. Bronson, Inc. Setting Timeout options on the command line will also override their sub-suboptions in the .cf file, e.g., -O Timeout.queuereturn=2d will set all queuereturn timeouts to 2 days. Problem noted by Roger B.A. Klorese. Portability: BSD/OS has a broken setreuid() implementation. Problem noted by Vernon Schryver of Rhyolite Software. BSD/OS has /dev/urandom(4) (as of version 4.1/199910 ?). Noted by Vernon Schryver of Rhyolite Software. BSD/OS has fchown(2). Noted by Dave Yadallee of Netline 2000 Internet Solutions Inc. Solaris 2.X and later have strerror(3). From Sebastian Hagedorn of Cologne University. CONFIG: Fix parsing for IPv6 domain literals in addresses (user@[IPv6:address]). Problem noted by Liyuan Zhou. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Comment: Processed by Mailcrypt 3.5.6, an Emacs/PGP interface Charset: noconv iQCVAwUBO2dFIHxLZ22gDhVjAQFcFQP/XnLbZR/F+NuLIxMr7piwmcwdsfyIZiBL Qn93ZuJMFIY5bYvAkVMa9tTxp71cRm9JM8oOwY2UimrNo7U40VHNBkOgLLvuYOlH L3PJ5jBd3PbW4waOer0GTw1kN3E026qX5Uh05sKFjXEOCpziyyNSYoMYbUDl59+I dX/l9uB1Raw= =hiC4 -----END PGP SIGNATURE----- -- �Desea desuscribirse? Escriba a [EMAIL PROTECTED] con el tema "unsubscribe".
