1f7f0659c6
upstream changes:
-----------------
Fix for an Exim interoperability problem when postscreen after-220 checks
are enabled. Bug introduced in Postfix 3.4: the code that detected
"PIPELINING after BDAT" looked at the wrong variable. The warning now says
"BDAT without valid RCPT", and the error is no longer treated as a command
PIPELINING error, thus allowing mail to be delivered. Meanwhile, Exim has
been fixed to stop sending BDAT commands when postscreen rejects all RCPT
commands.
Usability bug, introduced in Postfix 3.4: the parser for key/certificate
chain files rejected inputs that contain an EC PARAMETERS object. While
this is technically correct (the documentation says what types are allowed)
this is surprising behavior because the legacy cert/key parameters will
accept such inputs. For now, the parser skips object types that it does not
know about for usability, and logs a warning because ignoring inputs is not
kosher.
Bug introduced in Postfix 2.8: don't gratuitously enable all after-220
tests when only one such test is enabled. This made selective tests
impossible with 'good' clients. This will be fixed in older Postfix
versions at some later time.
10 lines
664 B
Text
10 lines
664 B
Text
$NetBSD: distinfo,v 1.182 2019/12/09 08:45:14 triaxx Exp $
|
|
|
|
SHA1 (postfix-3.4.8.tar.gz) = a6f90324fcba80eb59d4c9a6a2198421360252b7
|
|
RMD160 (postfix-3.4.8.tar.gz) = 430c5294a1fd4ca5411e13fb328897e01a03a055
|
|
SHA512 (postfix-3.4.8.tar.gz) = 782fe83e4b40c7aadfb4c55850db4c7163dd0f647f4ef133e59f7b47c993b2b4fa6c43ebbc45131caa54d968259f9c8568f47e81bfccda02ab142be52aa95d45
|
|
Size (postfix-3.4.8.tar.gz) = 4573099 bytes
|
|
SHA1 (patch-aa) = c8216f133e202a7bb37682b0dbc1448f021e7c1c
|
|
SHA1 (patch-ag) = c126c572e36bf2bcbd3f6e5d8332a3d26e704109
|
|
SHA1 (patch-ai) = 51748ccf92da543f7ff640f36906a29b5db3f6e3
|
|
SHA1 (patch-src_dns_dns__lookup.c) = 88cdda55765799d40f05fa7aad43cdbc58c4a307
|