From: Wietse Venema Date: Mon, 10 Dec 2012 05:00:00 +0000 (-0500) Subject: postfix-2.10-20121210 X-Git-Tag: v2.10.0-RC1~9 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b046cb2c8a3ac15307365a71a25804edbee87e32;p=thirdparty%2Fpostfix.git postfix-2.10-20121210 --- diff --git a/postfix/HISTORY b/postfix/HISTORY index 485b4298f..18a553df8 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -18045,7 +18045,7 @@ Apologies for any names omitted. Documentation: a simpler null-client example. File: proto/STANDARD_CONFIGURATION_README.html -20120113 +20121013 Cleanup: to compute the LDAP connection cache lookup key, join the numeric fields with null, just like string fields. @@ -18061,18 +18061,19 @@ Apologies for any names omitted. 20121022 - Bugfix (introduced 20101009) don't complain abuot stray -m + Bugfix (introduced 20101009) don't complain about stray -m option if none of -[bhm] is specified. Ralf Hildebrandt. File: postmap/postmap.c. 20121029 - Strip datalink suffix from IPv6 addresses returned by the - system getaddrinfo() routine. Such suffixes mess up the - default mynetworks value, host name/address verification - and possibly more. This change obsoletes the 20101108 change - that removes datalink suffixes in the SMTP and QMQP servers. - Files: util/myaddrinfo.c, smtpd/smtpd_peer.c, qmqpd/qmqpd_peer.c. + Workaround: strip datalink suffix from IPv6 addresses + returned by the system getaddrinfo() routine. Such suffixes + mess up the default mynetworks value, host name/address + verification and possibly more. This change obsoletes the + 20101108 change that removes datalink suffixes in the SMTP + and QMQP servers. Files: util/myaddrinfo.c, smtpd/smtpd_peer.c, + qmqpd/qmqpd_peer.c. 20121031 @@ -18087,7 +18088,7 @@ Apologies for any names omitted. postscreen/postscreen_smtpd.c, proto/POSTSCREEN_README.html. Bugfix (introduced: Postfix 1.1): wrong string termination - when handling a MBOX From_ line at the start of a message. + when handling an MBOX From_ line at the start of a message. File: qmqpd/qmqpd.c. 20121110 @@ -18120,3 +18121,22 @@ Apologies for any names omitted. Cleanup: consistent escaping of commands in postscreen deep protocol test logging. File: postscreen/postscreen_smtpd.c. + +20121124 + + Documentation: the bounce behavior for automatically-added + BCC recipients has changed with Postfix 2.3 when DSN support + was introduced. File: proto/postconf.proto. + +20121203 + + Documentation: added explicit example for -o name=value. + File: proto/master. + +20121210 + + Bugfix (introduced: Postfix 2.9) nesting count error while + stripping the optional [] around a DNS[BW]L address pattern. + This part of the code is not documented and had escaped + testing. Files: util/ip_match.c, util/ip_match.in, + util/ip_match.ref. diff --git a/postfix/README_FILES/POSTSCREEN_README b/postfix/README_FILES/POSTSCREEN_README index 6c59a5d14..a7253c670 100644 --- a/postfix/README_FILES/POSTSCREEN_README +++ b/postfix/README_FILES/POSTSCREEN_README @@ -13,10 +13,6 @@ process. By keeping spambots away, postscreen(8) leaves more SMTP server processes available for legitimate clients, and delays the onset of server overload conditions. -postscreen(8) maintains a temporary whitelist for clients that pass its tests; -by allowing whitelisted clients to skip tests, postscreen(8) minimizes its -impact on legitimate email traffic. - postscreen(8) should not be used on SMTP ports that receive mail from end-user clients (MUAs). In a typical deployment, postscreen(8) handles the MX service on TCP port 25, while MUA clients submit mail via the submission service on TCP @@ -24,6 +20,10 @@ port 587 which requires client authentication. Alternatively, a site could set up a dedicated, non-postscreen, "port 25" server that provides submission service and client authentication, but no MX service. +postscreen(8) maintains a temporary whitelist for clients that pass its tests; +by allowing whitelisted clients to skip tests, postscreen(8) minimizes its +impact on legitimate email traffic. + postscreen(8) is part of a multi-layer defense. * As the first layer, postscreen(8) blocks connections from zombies and other diff --git a/postfix/WISHLIST b/postfix/WISHLIST index b9dd0be81..130a442d4 100644 --- a/postfix/WISHLIST +++ b/postfix/WISHLIST @@ -11,6 +11,9 @@ Wish list: Don't forget Apple's code donation for fetching mail from IMAP server. + Make errno white/blacklist for getpwnam_r etc. and mailbox + write errors. + smtpd_muble_restrictions rule names are case-insensitive. restriction_classes values are case-sensitive but should be case-insensitive for consistency with smtpd_muble_restrictions. diff --git a/postfix/html/POSTSCREEN_README.html b/postfix/html/POSTSCREEN_README.html index ba47369e9..ca007ed3f 100644 --- a/postfix/html/POSTSCREEN_README.html +++ b/postfix/html/POSTSCREEN_README.html @@ -28,11 +28,6 @@ talk to a Postfix SMTP server process. By keeping spambots away, legitimate clients, and delays the onset of server overload conditions.

-

postscreen(8) maintains a temporary whitelist for clients that -pass its tests; by allowing whitelisted clients to skip tests, -postscreen(8) minimizes its impact on legitimate email traffic. -

-

postscreen(8) should not be used on SMTP ports that receive mail from end-user clients (MUAs). In a typical deployment, postscreen(8) handles the MX service on TCP port 25, while MUA @@ -41,6 +36,11 @@ requires client authentication. Alternatively, a site could set up a dedicated, non-postscreen, "port 25" server that provides submission service and client authentication, but no MX service.

+

postscreen(8) maintains a temporary whitelist for clients that +pass its tests; by allowing whitelisted clients to skip tests, +postscreen(8) minimizes its impact on legitimate email traffic. +

+

postscreen(8) is part of a multi-layer defense.