X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/870f6ba8a2945754a7f2f66097e3a64465fe1a04..eba0c039a556478f50aa1e4839684027746197f7:/doc/doc-txt/NewStuff?ds=sidebyside diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index e0d87c44a..bbf27010d 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.45 2005/05/23 16:58:55 fanf2 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.76 2005/10/03 13:25:32 ph10 Exp $ New Features in Exim -------------------- @@ -8,6 +8,176 @@ but have not yet made it into the main manual (which is most conveniently updated when there is a relatively large batch of changes). The doc/ChangeLog file contains a listing of all changes, including bug fixes. +Exim version 4.54 +----------------- + +There was a problem with 4.52/TF/02 in that a "name=" option on control= +submission terminated at the next slash, thereby not allowing for slashes in +the name. This has been changed so that "name=" takes the rest of the string as +its data. It must therefore be the last option. + + + +Exim version 4.53 +----------------- + +TK/01 Added the "success_on_redirect" address verification option. When an + address generates new addresses during routing, Exim will abort + verification with "success" when more than one address has been + generated, but continue to verify a single new address. The latter + does not happen when the new "success_on_redirect" option is set, like + + require verify = recipient/success_on_redirect/callout=10s + + In that case, verification will succeed when a router generates a new + address. + +PH/01 Support for SQLite database lookups has been added. This is another + query-style lookup, but it is slightly different from the others because + a file name is required in addition to the SQL query. This is because an + SQLite database is a single file and there is no daemon as in other SQL + databases. The interface to Exim requires the name of the file, as an + absolute path, to be given at the start of the query. It is separated + from the query by white space. This means that the path name cannot + contain white space. Here is a lookup expansion example: + + ${lookup sqlite {/some/thing/sqlitedb \ + select name from aliases where id='ph10';}} + + In a list, the syntax is similar. For example: + + domainlist relay_domains = sqlite;/some/thing/sqlitedb \ + select * from relays where ip='$sender_host_address'; + + The only character affected by the ${quote_sqlite: operator is a single + quote, which it doubles. + + The SQLite library handles multiple simultaneous accesses to the database + internally. Multiple readers are permitted, but only one process can + update at once. Attempts to access the database while it is being updated + are rejected after a timeout period, during which the SQLite library + waits for the lock to be released. In Exim, the default timeout is set + to 5 seconds, but it can be changed by means of the sqlite_lock_timeout + option. + + Note that you must set LOOKUP_SQLITE=yes in Local/Makefile in order to + obtain SQLite support, and you will also need to add -lsqlite3 to the + EXTRALIBS setting. And of course, you have to install SQLite on your + host first. + +PH/02 The variable $message_id is now deprecated, to be replaced by + $message_exim_id, which makes it clearer which ID is being referenced. + +PH/03 The use of forbid_filter_existstest now also locks out the use of the + ${stat: expansion item. + +PH/04 The IGNOREQUOTA extension to the LMTP protocol is now available in both + the lmtp transport and the smtp transport running in LMTP mode. In the + lmtp transport there is a new Boolean option called ignore_quota, and in + the smtp transport there is a new Boolean option called + lmtp_ignore_quota. If either of these options is set TRUE, the string + "IGNOREQUOTA" is added to RCPT commands when using the LMTP protocol, + provided that the server has advertised support for IGNOREQUOTA in its + response to the LHLO command. + +PH/05 Previously, if "verify = helo" was set in an ACL, the condition was true + only if the host matched helo_try_verify_hosts, which caused the + verification to occur when the EHLO/HELO command was issued. The ACL just + tested the remembered result. Now, if a previous verification attempt has + not happened, "verify = helo" does it there and then. + +PH/06 It is now possible to specify a port number along with a host name or + IP address in the list of hosts defined in the manualroute or + queryprogram routers, fallback_hosts, or the "hosts" option of the smtp + transport. These all override any port specification on the transport. + The relatively standard syntax of using a colon separator has been + adopted, but there are some gotchas that need attention: + + * In all these lists of hosts, colon is the default separator, so either + the colon that specifies a port must be doubled, or the separator must + be changed. The following two examples have the same effect: + + fallback_hosts = host1.tld::1225 : host2.tld::1226 + fallback_hosts = <; host1.tld:1225 ; host2.tld:1226 + + * When IPv6 addresses are involved, it gets worse, because they contain + colons of their own. To make this case easier, it is permitted to + enclose an IP address (either v4 or v6) in square brackets if a port + number follows. Here's an example from a manualroute router: + + route_list = * "" and "MAIL FROM: <>". + +TF/01 There's a new script in util/ratelimit.pl which extracts sending + rates from log files, to assist with choosing appropriate settings + when deploying the ratelimit ACL condition. + +PH/13 A new letter, "H", is available in retry parameter sets. It is similar + to "G" (geometric increasing time intervals), except that the interval + before the next retry is randomized. Each time, the previous interval is + multiplied by the factor in order to get a maximum for the next interval. + The mininum interval is the first argument of the parameter, and an + actual interval is chosen randomly between them. Such a rule has been + found to be helpful in cluster configurations when all the members of the + cluster restart at once, and may synchronize their queue processing + times. + +PH/14 The options never_users, trusted_users, admin_groups, and trusted_groups + are now expanded when the configuration file is read. + Exim version 4.52 ----------------- @@ -132,8 +302,8 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure ratelimit = /

/ / - If the average client sending rate is greater than m messages per time - period p then the condition is true, otherwise it is false. + If the average client sending rate is less than m messages per time + period p then the condition is false, otherwise it is true. The parameter p is the smoothing time constant, in the form of an Exim time interval e.g. 8h for eight hours. A larger time constant means it @@ -144,16 +314,23 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure rate limit. Conversely, if m and p are both small then messages must be sent at an even rate. - The key is used to look up the data used to calcluate the client's + The key is used to look up the data used to calculate the client's average sending rate. This data is stored in a database maintained by Exim in its spool directory alongside the retry database etc. For example, you can limit the sending rate of each authenticated user, independent of the computer they are sending from, by setting the key to $authenticated_id. The default key is $sender_host_address. + Internally, Exim includes the smoothing constant p and the options in + the lookup key because they alter the meaning of the stored data. + This is not true for the limit m, so you can alter the configured + maximum rate and Exim will still remember clients' past behaviour, + but if you alter the other ratelimit parameters Exim will effectively + forget their past behaviour. Each ratelimit condition can have up to two options. The first option specifies what Exim measures the rate of, and the second specifies how - Exim handles excessively fast clients. + Exim handles excessively fast clients. The options are separated by a + slash, like the other parameters. The per_mail option means that it measures the client's rate of sending messages. This is the default if none of the per_* options is specified. @@ -186,7 +363,12 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure updated. The effect of this is that Exim measures the client's average rate of attempts to send email, which can be much higher than the maximum. If the client is over the limit it will be subjected to - counter-measures until it slows down below the maximum rate. + counter-measures until it slows down below the maximum rate. The + smoothing period determines the time it takes for a high sending rate + to decay exponentially to 37% of its peak value, which means that you + can work out the time (the number of smoothing periods) that a client + is subjected to counter-measures after an over-limit burst with the + formula ln(peakrate/maxrate). The leaky option means that the client's recorded rate is not updated if it is above the limit. The effect of this is that Exim measures the @@ -209,13 +391,12 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure # Log all senders' rates warn ratelimit = 0 / 1h / strict - log_message = \ - Sender rate $sender_rate > $sender_rate_limit / $sender_rate_period + log_message = Sender rate $sender_rate / $sender_rate_period # Slow down fast senders warn ratelimit = 100 / 1h / per_rcpt / strict - delay = ${eval: 10 * ($sender_rate - $sender_rate_limit) } + delay = ${eval: $sender_rate - $sender_rate_limit }s # Keep authenticated users under control deny @@ -229,12 +410,176 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure # Restrict incoming rate from each host, with a default rate limit # set using a macro and special cases looked up in a table. defer - message = Sender rate $sender_rate exceeds \ - $sender_rate_limit messages per $sender_rate_period + message = Sender rate exceeds $sender_rate_limit \ + messages per $sender_rate_period ratelimit = ${lookup {$sender_host_address} \ cdb {DB/ratelimits.cdb} \ {$value} {RATELIMIT} } + Warning: if you have a busy server with a lot of ratelimit tests, + especially with the per_rcpt option, you may suffer from a performance + bottleneck caused by locking on the ratelimit hints database. Apart from + making your ACLs less complicated, you can reduce the problem by using a + RAM disk for Exim's hints directory, /var/spool/exim/db/. However this + means that Exim will lose its hints data after a reboot (including retry + hints, the callout cache, and ratelimit data). + +TK/01 Added an 'spf' lookup type that will return an SPF result for a given + email address (the key) and an IP address (the database): + + ${lookup {tom@duncanthrax.net} spf{217.115.139.137}} + + The lookup will return the same result strings as they can appear in + $spf_result (pass,fail,softfail,neutral,none,err_perm,err_temp). The + lookup is armored in EXPERIMENTAL_SPF. Currently, only IPv4 addresses + are supported. + + Patch submitted by Chris Webb . + +PH/02 There's a new verify callout option, "fullpostmaster", which first acts + as "postmaster" and checks the recipient . If that + fails, it tries just , without a domain, in accordance with + the specification in RFC 2821. + +PH/03 The action of the auto_thaw option has been changed. It no longer applies + to frozen bounce messages. + +TK/02 There are two new expansion items to help with the implementation of + the BATV "prvs" scheme in an Exim configuration: + + + ${prvs {

}{}{[KEYNUM]}} + + The "prvs" expansion item takes three arguments: A qualified RFC2821 + email address, a key and an (optional) key number. All arguments are + expanded before being used, so it is easily possible to lookup a key + and key number using the address as the lookup key. The key number is + optional and defaults to "0". The item will expand to a "prvs"-signed + email address, to be typically used with the "return_path" option on + a smtp transport. The decision if BATV should be used with a given + sender/recipient pair should be done on router level, to avoid having + to set "max_rcpt = 1" on the transport. + + + ${prvscheck {
}{}{}} + + The "prvscheck" expansion item takes three arguments. Argument 1 is + expanded first. When the expansion does not yield a SYNTACTICALLY + valid "prvs"-scheme address, the whole "prvscheck" item expands to + the empty string. If
is a "prvs"-encoded address after + expansion, two expansion variables are set up: + + $prvscheck_address Contains the "prvs"-decoded version of + the address from argument 1. + + $prvscheck_keynum Contains the key number extracted from + the "prvs"-address in argument 1. + + These two variables can be used in the expansion code of argument 2 + to retrieve the . The VALIDITY of the "prvs"-signed address + is then checked. The result is stored in yet another expansion + variable: + + $prvscheck_result Contains the result of a "prvscheck" + expansion: Unset (the empty string) for + failure, "1" for success. + + The "prvscheck" expansion expands to the empty string if
+ is not a SYNTACTICALLY valid "prvs"-scheme address. Otherwise, + argument 3 defines what "prvscheck" expands to: If argument 3 + is the empty string, "prvscheck" expands to the decoded version + of the address (no matter if it is CRYPTOGRAPHICALLY valid or not). + If argument 3 expands to a non-empty string, "prvscheck" expands + to that string. + + + Usage example + ------------- + + Macro: + + PRVSCHECK_SQL = ${lookup mysql{SELECT secret FROM batv_prvs WHERE \ + sender='${quote_mysql:$prvscheck_address}'}{$value}} + + RCPT ACL: + + # Bounces: drop unsigned addresses for BATV senders + deny message = This address does not send an unsigned reverse path. + senders = : + recipients = +batv_recipients + + # Bounces: In case of prvs-signed address, check signature. + deny message = Invalid reverse path signature. + senders = : + condition = ${prvscheck {$local_part@$domain}{PRVSCHECK_SQL}{1}} + !condition = $prvscheck_result + + Top-Level Router: + + batv_redirect: + driver = redirect + data = ${prvscheck {$local_part@$domain}{PRVSCHECK_SQL}{}} + + Transport (referenced by router that makes decision if + BATV is applicable): + + external_smtp_batv: + driver = smtp + return_path = ${prvs {$return_path} \ + {${lookup mysql{SELECT \ + secret FROM batv_prvs WHERE \ + sender='${quote_mysql:$sender_address}'} \ + {$value}fail}}} + +PH/04 There are two new options that control the retrying done by the daemon + at startup when it cannot immediately bind a socket (typically because + the socket is already in use). The default values reproduce what were + built-in constants previously: daemon_startup_retries defines the number + of retries after the first failure (default 9); daemon_startup_sleep + defines the length of time to wait between retries (default 30s). + +PH/05 There is now a new ${if condition called "match_ip". It is similar to + match_domain, etc. It must be followed by two argument strings. The first + (after expansion) must be an IP address or an empty string. The second + (after expansion) is a restricted host list that can match only an IP + address, not a host name. For example: + + ${if match_ip{$sender_host_address}{1.2.3.4:5.6.7.8}{...}{...}} + + The specific types of host list item that are permitted in the list are + shown below. Consult the manual section on host lists for further + details. + + . An IP address, optionally with a CIDR mask. + + . A single asterisk matches any IP address. + + . An empty item matches only if the IP address is empty. This could be + useful for testing for a locally submitted message or one from specific + hosts in a single test such as + + ${if match_ip{$sender_host_address}{:4.3.2.1:...}{...}{...}} + + where the first item in the list is the empty string. + + . The item @[] matches any of the local host's interface addresses. + + . Lookups are assumed to be "net-" style lookups, even if "net-" is not + specified. Thus, the following are equivalent: + + ${if match_ip{$sender_host_address}{lsearch;/some/file}... + ${if match_ip{$sender_host_address}{net-lsearch;/some/file}... + + You do need to specify the "net-" prefix if you want to specify a + specific address mask, for example, by using "net24-". + +PH/06 The "+all" debug selector used to set the flags for all possible output; + it is something that people tend to use semi-automatically when + generating debug output for me or for the list. However, by including + "+memory", an awful lot of output that is very rarely of interest was + generated. I have changed this so that "+all" no longer includes + "+memory". However, "-all" still turns everything off. + Version 4.51 ------------