diff --git a/postfix/HISTORY b/postfix/HISTORY index 819cc78a7..31dd8cfc4 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -17629,3 +17629,35 @@ Apologies for any names omitted. to a missing guard statement after an smtpd_check_rewrite() call was moved closer to the command processor loop. Fix by Bartek Szady. File: smtpd/smtpd.c. + +20120220 + + Cleanup: documentation of how to use only system-supplied + certificates with *CAfile and *CApath. File: proto/postconf.proto. + + Cleanup: documentation of smtp_sasl_mechanism_filter. File: + proto/postconf.proto. + +20120222 + + Cleanup: when multiple DNSBLs block an SMTP client, the + postscreen "reject" message now gives credit to the DNSBL + with the largest weight, instead of the DNSBL that replies + first. File: postscreen/postscreeb_dnsbl.c. + + Cleanup: memcache_table(5) manpage. File proto/memcache_table. + +20120225 + + Cleanup: eliminated the build-time Perl dependency. File: + bounce/annotate.sh. + + Cleanup: when -DNO_DB support was added, the makedefs script + was not updated to skip the Linux Berkeley DB tests. + + FreeBSD9 is now a supported platform. Files: makedefs, + util/sys_defs.h. + +20120226 + + Cleanup: documentation in postfix-install. diff --git a/postfix/html/memcache_table.5.html b/postfix/html/memcache_table.5.html index 01da77ed3..36af14727 100644 --- a/postfix/html/memcache_table.5.html +++ b/postfix/html/memcache_table.5.html @@ -84,37 +84,38 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5) flags (default: 0) Optional flags that should be stored along with a - memcache update. + memcache update. The flags are ignored when looking + up information. ttl (default: 3600) The expiration time in seconds of memcache updates. - NOTE 1: When using a memcache table as + NOTE 1: When using a memcache table as postscreen(8) or verify(8) cache without persistent backup, specify a zero *_cache_cleanup_interval - value with all Postfix instances that use the mem- - cache, and specify the largest postscreen(8) *_ttl - value or verify(8) *_expire_time value as the mem- + value with all Postfix instances that use the mem- + cache, and specify the largest postscreen(8) *_ttl + value or verify(8) *_expire_time value as the mem- cache table's ttl value. - NOTE 2: According to memcache protocol documenta- - tion, a value greater than 30 days (2592000 sec- - onds) specifies absolute UNIX time. Smaller values + NOTE 2: According to memcache protocol documenta- + tion, a value greater than 30 days (2592000 sec- + onds) specifies absolute UNIX time. Smaller values are relative to the time of the update. MEMCACHE KEY PARAMETERS key_format (default: %s) - Format of the lookup and update keys in memcache - requests. By default, these are the same as the - lookup and update keys that are given to the Post- + Format of the lookup and update keys in memcache + requests. By default, these are the same as the + lookup and update keys that are given to the Post- fix memcache client. NOTE: The key_format feature is not used for backup database requests. - When the same memcache database is used to cache - information from multiple tables, you can use the - key_format feature to avoid name collisions by + When the same memcache database is used to cache + information from multiple tables, you can use the + key_format feature to avoid name collisions by prepending a fixed string. Examples: key_format = aliases:%s @@ -125,48 +126,48 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5) %% This is replaced by a literal '%' character. - %s This is replaced by the memcache client + %s This is replaced by the memcache client input key. %u When the input key is an address of the form user@domain, %u is replaced by the SQL - quoted local part of the address. Other- - wise, %u is replaced by the entire search + quoted local part of the address. Other- + wise, %u is replaced by the entire search string. If the localpart is empty, a lookup - is silently suppressed and returns no - results (an update is skipped with a warn- + is silently suppressed and returns no + results (an update is skipped with a warn- ing). %d When the input key is an address of the form - user@domain, %d is replaced by the domain + user@domain, %d is replaced by the domain part of the address. Otherwise, a lookup is - silently suppressed and returns no results + silently suppressed and returns no results (an update is skipped with a warning). %[SUD] The upper-case equivalents of the above - expansions behave in the key_format parame- + expansions behave in the key_format parame- ter identically to their lower-case counter- parts. - %[1-9] The patterns %1, %2, ... %9 are replaced by + %[1-9] The patterns %1, %2, ... %9 are replaced by the corresponding most significant component - of the input key's domain. If the input key + of the input key's domain. If the input key is user@mail.example.com, then %1 is com, %2 - is example and %3 is mail. If the input key + is example and %3 is mail. If the input key is unqualified or does not have enough - domain components to satisfy all the speci- - fied patterns, a lookup is silently sup- + domain components to satisfy all the speci- + fied patterns, a lookup is silently sup- pressed and returns no results (an update is skipped with a warning). domain (default: no domain list) This feature can significantly reduce database server load. Specify a list of domain names, paths - to files, or "type:table" databases. When speci- + to files, or "type:table" databases. When speci- fied, only fully qualified search keys with a *non- empty* localpart and a matching domain are eligible - for lookup or update: bare 'user' lookups, bare - domain lookups and "@domain" lookups are silently + for lookup or update: bare 'user' lookups, bare + domain lookups and "@domain" lookups are silently skipped (updates are skipped with a warning). Example: @@ -180,33 +181,33 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5) The maximal memcache reply line length in bytes. max_try (default: 2) - The number of times to try a memcache command - before giving up. The memcache client does not + The number of times to try a memcache command + before giving up. The memcache client does not retry a command when the memcache server accepts no connection. retry_pause (default: 1) - The time in seconds before retrying a failed mem- + The time in seconds before retrying a failed mem- cache command. timeout (default: 2) - The time limit for sending a memcache command and + The time limit for sending a memcache command and for receiving a memcache reply. BUGS - The Postfix memcache client cannot be used for security- - sensitive tables such as alias_maps (these may contain - "|command and "/file/name" destinations), or vir- - tual_uid_maps, virtual_gid_maps and virtual_mailbox_maps - (these specify UNIX process privileges or "/file/name" - destinations). In a typical deployment a memcache data- - base is writable by any process that can talk to the mem- - cache server; in contrast, security-sensitive tables must + The Postfix memcache client cannot be used for security- + sensitive tables such as alias_maps (these may contain + "|command and "/file/name" destinations), or vir- + tual_uid_maps, virtual_gid_maps and virtual_mailbox_maps + (these specify UNIX process privileges or "/file/name" + destinations). In a typical deployment a memcache data- + base is writable by any process that can talk to the mem- + cache server; in contrast, security-sensitive tables must never be writable by the unprivileged Postfix user. The Postfix memcache client requires additional configura- - tion when used as postscreen(8) or verify(8) cache. For - details see the backup and ttl parameter discussions in + tion when used as postscreen(8) or verify(8) cache. For + details see the backup and ttl parameter discussions in the MEMCACHE MAIN PARAMETERS section above. SEE ALSO @@ -218,11 +219,11 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5) MEMCACHE_README, Postfix memcache client guide LICENSE - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. HISTORY - Memcache support was introduced with Postfix version 2.9. + Memcache support was introduced with Postfix version 2.9. AUTHOR(S) Wietse Venema diff --git a/postfix/html/postconf.5.html b/postfix/html/postconf.5.html index ec54b00c4..81fb9221a 100644 --- a/postfix/html/postconf.5.html +++ b/postfix/html/postconf.5.html @@ -10201,10 +10201,10 @@ parameter, but the setting "no" does not.
If non-empty, a Postfix SMTP client filter for the remote SMTP server's list of offered SASL mechanisms. Different client and -server implementations may support different mechanism lists. By +server implementations may support different mechanism lists; by default, the Postfix SMTP client will use the intersection of the -two. smtp_sasl_mechanism_filter further restricts what server -mechanisms the client will take into consideration.
+two. smtp_sasl_mechanism_filter specifies an optional third mechanism +list to intersect with.Specify mechanism names, "/file/name" patterns or "type:table" lookup tables. The right-hand side result from "type:table" lookups @@ -10490,6 +10490,10 @@ file may also be used to augment the client certificate trust chain, but it is best to include all the required certificates directly in $smtp_tls_cert_file.
+Specify "smtp_tls_CAfile = /path/to/system_CA_file" to use +ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -10517,6 +10521,10 @@ with, for example, "$OPENSSL_HOME/bin/c_rehash /etc/postfix/certs".To use this option in chroot mode, this directory (or a copy) must be inside the chroot jail.
+Specify "smtp_tls_CApath = /path/to/system_CA_directory" to +use ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -14196,6 +14204,10 @@ file may also be used to augment the server certificate trust chain, but it is best to include all the required certificates directly in the server certificate file. +Specify "smtpd_tls_CAfile = /path/to/system_CA_file" to use ONLY +the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -14231,6 +14243,10 @@ for example, "$OPENSSL_HOME/bin/c_rehash /etc/postfix/certs". To use smtpd_tls_CApath in chroot mode, this directory (or a copy) must be inside the chroot jail. +Specify "smtpd_tls_CApath = /path/to/system_CA_directory" to +use ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
diff --git a/postfix/makedefs b/postfix/makedefs index 316d94b48..92a9717c3 100644 --- a/postfix/makedefs +++ b/postfix/makedefs @@ -153,6 +153,8 @@ case "$SYSTEM.$RELEASE" in ;; FreeBSD.8*) SYSTYPE=FREEBSD8 ;; + FreeBSD.9*) SYSTYPE=FREEBSD9 + ;; OpenBSD.2*) SYSTYPE=OPENBSD2 ;; OpenBSD.3*) SYSTYPE=OPENBSD3 @@ -267,36 +269,31 @@ case "$SYSTEM.$RELEASE" in esac;; # Tested with RedHat 3.03 on 20020729. Linux.1*) SYSTYPE=LINUX1 - SYSLIBS="-ldb" + case "$CCARGS" in + *-DNO_DB*) ;; + *) SYSLIBS="-ldb";; + esac ;; Linux.2*) SYSTYPE=LINUX2 - # Postfix no longer needs DB 1.85 compatibility - if [ -f /usr/include/db.h ] - then - : we are all set - elif [ -f /usr/include/db/db.h ] - then - CCARGS="$CCARGS -I/usr/include/db" - else - # No, we're not going to try db1 db2 db3 etc. - # On a properly installed system, Postfix builds - # by includingIf non-empty, a Postfix SMTP client filter for the remote SMTP server's list of offered SASL mechanisms. Different client and -server implementations may support different mechanism lists. By +server implementations may support different mechanism lists; by default, the Postfix SMTP client will use the intersection of the -two. smtp_sasl_mechanism_filter further restricts what server -mechanisms the client will take into consideration.
+two. smtp_sasl_mechanism_filter specifies an optional third mechanism +list to intersect with.Specify mechanism names, "/file/name" patterns or "type:table" lookup tables. The right-hand side result from "type:table" lookups @@ -8811,6 +8811,10 @@ file may also be used to augment the server certificate trust chain, but it is best to include all the required certificates directly in the server certificate file.
+Specify "smtpd_tls_CAfile = /path/to/system_CA_file" to use ONLY +the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -8842,6 +8846,10 @@ for example, "$OPENSSL_HOME/bin/c_rehash /etc/postfix/certs". To use smtpd_tls_CApath in chroot mode, this directory (or a copy) must be inside the chroot jail. +Specify "smtpd_tls_CApath = /path/to/system_CA_directory" to +use ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -9221,6 +9229,10 @@ file may also be used to augment the client certificate trust chain, but it is best to include all the required certificates directly in $smtp_tls_cert_file. +Specify "smtp_tls_CAfile = /path/to/system_CA_file" to use +ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
@@ -9244,6 +9256,10 @@ with, for example, "$OPENSSL_HOME/bin/c_rehash /etc/postfix/certs".To use this option in chroot mode, this directory (or a copy) must be inside the chroot jail.
+Specify "smtp_tls_CApath = /path/to/system_CA_directory" to +use ONLY the system-supplied default certificate authority certificates. +
+Specify "tls_append_default_CA = no" to prevent Postfix from appending the system-supplied default CAs and trusting third-party certificates.
diff --git a/postfix/src/bounce/Makefile.in b/postfix/src/bounce/Makefile.in index 09de6e9d0..8c98151db 100644 --- a/postfix/src/bounce/Makefile.in +++ b/postfix/src/bounce/Makefile.in @@ -25,9 +25,9 @@ $(PROG): $(OBJS) $(LIBS) $(CC) $(CFLAGS) -o $@ $(OBJS) $(LIBS) $(SYSLIBS) # Eliminate dependency on installed Postfix. -../../conf/bounce.cf.default: template_test.ref annotate.pl +../../conf/bounce.cf.default: template_test.ref annotate.sh rm -f $@ - perl annotate.pl