From: Wietse Venema Date: Mon, 26 Dec 2005 05:00:00 +0000 (-0500) Subject: postfix-2.3-20051226 X-Git-Tag: v2.3-RC1~29 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bb0be7749b5ead8456ae48e430106247be7566b7;p=thirdparty%2Fpostfix.git postfix-2.3-20051226 --- diff --git a/postfix/HISTORY b/postfix/HISTORY index b18936090..b17574f33 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -11660,6 +11660,23 @@ Apologies for any names omitted. Bugfix: 20051219 "postconf -A" produced "postconf -a" output. Andreas Winkelmann. +20051225 + + Bugfix: the regexp map cleverly avoided scanning constant + lookup results for non-existent $number expressions, but + failed to subject those results to the necessary $$ -> $ + replacement. Files: util/dict_regexp.c. + + Performance: the pcre map did not optimize constant lookup + results; they were always scanned for non-existent $number + expressions. File: util/dict_pcre.c. + + This round of edits eliminates architectural differences + between the pcre and regexp table implementations. The + remaining difference is that regexp tables still support + the obsolete "/pattern1/!/pattern2/ action" syntax, for + backwards compatibility with Postfix 2.0 and earlier. + Open problems: "postsuper -r" no longer resets the message arrival time, @@ -11670,11 +11687,6 @@ Open problems: Is it safe to cache a connection after it has been used for more than some number of address verification probes? - Access map actions such as FILTER and REDIRECT don't work - in smtpd_end_of_data_restrictions (or anything else that - generates additional queue file records after the message - content is stored). - Try to recognize that Resent- headers appear in blocks, newest block first. But don't break on incorrect header block organization. diff --git a/postfix/README_FILES/DSN_README b/postfix/README_FILES/DSN_README index 25f4d917d..b7bc3fd10 100644 --- a/postfix/README_FILES/DSN_README +++ b/postfix/README_FILES/DSN_README @@ -10,7 +10,9 @@ delivery notifications. Specifically, DSN support gives an email sender the ability to specify: - * What notifications are sent: success, failure, delay, or none. + * What notifications are sent: success, failure, delay, or none. Normally, + Postfix informs the sender only mail when delivery is delayed or when + delivery fails. * What content is returned in case of failure: only the message headers, or the full message. @@ -37,9 +39,11 @@ Unfortunately, disallowing "success" notification requests requires disallowing other DSN requests as well. The RFCs do not offer the option to negotiate feature subsets. -This is not as bad as it sounds. Remote senders with DSN support will still be -informed that their mail reached your Postfix gateway successfully; they just -will not get successful delivery notices from your internal systems. +This is not as bad as it sounds. When you turn off DSN for remote inbound mail, +remote senders with DSN support will still be informed that their mail reached +your Postfix gateway successfully; they just will not get successful delivery +notices from your internal systems. Remote senders lose very little: they can +no longer specify how Postfix should report delayed or failed delivery. Use the smtpd_discard_ehlo_keyword_address_maps feature if you wish to allow DSN requests from trusted clients but not from random strangers (see below for diff --git a/postfix/conf/access b/postfix/conf/access index bacefdaa6..515ee6d2f 100644 --- a/postfix/conf/access +++ b/postfix/conf/access @@ -221,33 +221,27 @@ # transport(5) table to direct mail to the discard(8) # service. # -# Note: this action does not work in Postfix 2.2 -# smtpd_end_of_data_restrictions. -# # This feature is available in Postfix 2.0 and later. # -# DUNNO Pretend that the lookup key was not found. This -# prevents Postfix from trying substrings of the -# lookup key (such as a subdomain name, or a network +# DUNNO Pretend that the lookup key was not found. This +# prevents Postfix from trying substrings of the +# lookup key (such as a subdomain name, or a network # address subnetwork). # # This feature is available in Postfix 2.0 and later. # # FILTER transport:destination -# After the message is queued, send the entire mes- +# After the message is queued, send the entire mes- # sage through the specified external content filter. -# The transport:destination syntax is described in -# the transport(5) manual page. More information -# about external content filters is in the Postfix +# The transport:destination syntax is described in +# the transport(5) manual page. More information +# about external content filters is in the Postfix # FILTER_README file. # -# Note: this action overrides the main.cf con- +# Note: this action overrides the main.cf con- # tent_filter setting, and currently affects all # recipients of the message. # -# Note: this action does not work in Postfix 2.2 -# smtpd_end_of_data_restrictions. -# # This feature is available in Postfix 2.0 and later. # # HOLD optional text... @@ -268,37 +262,31 @@ # Note: this action currently affects all recipients # of the message. # -# Note: this action does not work in Postfix 2.2 -# smtpd_end_of_data_restrictions. -# # This feature is available in Postfix 2.0 and later. # # PREPEND headername: headervalue -# Prepend the specified message header to the mes- +# Prepend the specified message header to the mes- # sage. When this action is used multiple times, the -# first prepended header appears before the second +# first prepended header appears before the second # etc. prepended header. # -# Note: this action does not support multi-line mes- +# Note: this action does not support multi-line mes- # sage headers. # -# Note: this action must be used before the message -# content is received; it cannot be used in +# Note: this action must be used before the message +# content is received; it cannot be used in # smtpd_end_of_data_restrictions. # # This feature is available in Postfix 2.1 and later. # # REDIRECT user@domain -# After the message is queued, send the message to +# After the message is queued, send the message to # the specified address instead of the intended # recipient(s). # -# Note: this action overrides the FILTER action, and +# Note: this action overrides the FILTER action, and # currently affects all recipients of the message. # -# Note: this action does not work in Postfix 2.2 -# smtpd_end_of_data_restrictions. -# # This feature is available in Postfix 2.1 and later. # # WARN optional text... diff --git a/postfix/html/DSN_README.html b/postfix/html/DSN_README.html index 41c529113..38d1efe71 100644 --- a/postfix/html/DSN_README.html +++ b/postfix/html/DSN_README.html @@ -30,7 +30,8 @@ specify: