openbsd-ports/mail/exim/distinfo

MD5 (exim-3.34.tar.gz) = ef0e1116acce2849701691fd159ad204
MD5 (exim-texinfo-3.30.tar.gz) = 155ae0ece6c4b50f7c0a8f7d9e2d0944
RMD160 (exim-3.34.tar.gz) = d695d5e37c9b39a1ae1320c5eefd76a41bdc989d
RMD160 (exim-texinfo-3.30.tar.gz) = 7e2d7e1fa2ef7ff82e0b8d97abde673d7d2df004
SHA1 (exim-3.34.tar.gz) = e545dd11e49d57a25ca6b2cd112c2f899bb7c497
SHA1 (exim-texinfo-3.30.tar.gz) = d7b8ee14da0cf7ba5f8f425b3cd109117bedc0d3
From the ChangeLog: Version 3.34 ------------ 1. Exim was failing to diagnose a lone \ at the end of an expansion string as an error (basically a typo in the code). 2. If logging was only to syslog, and Exim was trying to panic-die, it crashed instead of dying cleanly. 3. If an address was routed using a DNS lookup that found no MX records, but one or more A records, and fallback hosts were specified on the transport, the fallback hosts were ignored. 4. $message_body_size was set incorrectly (to zero) during filter testing. 5. Ensure the configuration file is closed before running the -bi command. 6. Reap all complete processes within the loop for accepting -bs or -bS messages, because it seems that not all OS do this automatically when SIGCHLD is set to SIG_IGN. 7. Reset SIGHUP to SIG_IGN before restarting a daemon, in case another SIGHUP arrives very quickly and kills the newly started Exim before it has a chance to get going. 8. After "452 space shortage", was not unsetting the sender address. Could lead to strange effects when the client was pipelining. 9. There was no check that getpeername() was giving a socket address when called on stdin passed from a previous delivery. 10. If a local part beginning with a pipe symbol was directed to a pipe transport, the transport got confused as to which command it should run. This could be a security exposure if unchecked local parts are directed or routed to pipe transports. 2001-12-29 07:55:08 -05:00			`MD5 (exim-3.34.tar.gz) = ef0e1116acce2849701691fd159ad204`
update to exim 3.30 This does not yet include the IPv6 / IPv4 OpenBSD patch discussed on various lists. 2001-07-25 04:18:48 -04:00			`MD5 (exim-texinfo-3.30.tar.gz) = 155ae0ece6c4b50f7c0a8f7d9e2d0944`
From the ChangeLog: Version 3.34 ------------ 1. Exim was failing to diagnose a lone \ at the end of an expansion string as an error (basically a typo in the code). 2. If logging was only to syslog, and Exim was trying to panic-die, it crashed instead of dying cleanly. 3. If an address was routed using a DNS lookup that found no MX records, but one or more A records, and fallback hosts were specified on the transport, the fallback hosts were ignored. 4. $message_body_size was set incorrectly (to zero) during filter testing. 5. Ensure the configuration file is closed before running the -bi command. 6. Reap all complete processes within the loop for accepting -bs or -bS messages, because it seems that not all OS do this automatically when SIGCHLD is set to SIG_IGN. 7. Reset SIGHUP to SIG_IGN before restarting a daemon, in case another SIGHUP arrives very quickly and kills the newly started Exim before it has a chance to get going. 8. After "452 space shortage", was not unsetting the sender address. Could lead to strange effects when the client was pipelining. 9. There was no check that getpeername() was giving a socket address when called on stdin passed from a previous delivery. 10. If a local part beginning with a pipe symbol was directed to a pipe transport, the transport got confused as to which command it should run. This could be a security exposure if unchecked local parts are directed or routed to pipe transports. 2001-12-29 07:55:08 -05:00			`RMD160 (exim-3.34.tar.gz) = d695d5e37c9b39a1ae1320c5eefd76a41bdc989d`
update to exim 3.30 This does not yet include the IPv6 / IPv4 OpenBSD patch discussed on various lists. 2001-07-25 04:18:48 -04:00			`RMD160 (exim-texinfo-3.30.tar.gz) = 7e2d7e1fa2ef7ff82e0b8d97abde673d7d2df004`
From the ChangeLog: Version 3.34 ------------ 1. Exim was failing to diagnose a lone \ at the end of an expansion string as an error (basically a typo in the code). 2. If logging was only to syslog, and Exim was trying to panic-die, it crashed instead of dying cleanly. 3. If an address was routed using a DNS lookup that found no MX records, but one or more A records, and fallback hosts were specified on the transport, the fallback hosts were ignored. 4. $message_body_size was set incorrectly (to zero) during filter testing. 5. Ensure the configuration file is closed before running the -bi command. 6. Reap all complete processes within the loop for accepting -bs or -bS messages, because it seems that not all OS do this automatically when SIGCHLD is set to SIG_IGN. 7. Reset SIGHUP to SIG_IGN before restarting a daemon, in case another SIGHUP arrives very quickly and kills the newly started Exim before it has a chance to get going. 8. After "452 space shortage", was not unsetting the sender address. Could lead to strange effects when the client was pipelining. 9. There was no check that getpeername() was giving a socket address when called on stdin passed from a previous delivery. 10. If a local part beginning with a pipe symbol was directed to a pipe transport, the transport got confused as to which command it should run. This could be a security exposure if unchecked local parts are directed or routed to pipe transports. 2001-12-29 07:55:08 -05:00			`SHA1 (exim-3.34.tar.gz) = e545dd11e49d57a25ca6b2cd112c2f899bb7c497`
update to exim 3.30 This does not yet include the IPv6 / IPv4 OpenBSD patch discussed on various lists. 2001-07-25 04:18:48 -04:00			`SHA1 (exim-texinfo-3.30.tar.gz) = d7b8ee14da0cf7ba5f8f425b3cd109117bedc0d3`