A "Completed" log line is now written for messages that are removed from
[exim.git] / doc / doc-txt / NewStuff
4deaf07d 1$Cambridge: exim/doc/doc-txt/NewStuff,v 1.6 2004/11/04 12:19:48 ph10 Exp $
3New Features in Exim
6This file contains descriptions of new features that have been added to Exim,
7but have not yet made it into the main manual (which is most conveniently
8updated when there is a relatively large batch of changes). The doc/ChangeLog
9file contains a listing of all changes, including bug fixes.
12Version 4.44
15 1. There is a new build-time option called CONFIGURE_GROUP which works like
16 CONFIGURE_OWNER. It specifies one additional group that is permitted for
17 the runtime configuration file when the group write permission is set.
19 2. The "control=submission" facility has a new option /retain_sender. This
20 has the effect of setting local_sender_retain true and local_from_check
21 false for the incoming message in which it is encountered.
23 3. $recipients is now available in the predata ACL (oversight).
25 4. The value of address_data from a sender verification is now available in
26 $sender_address_data in subsequent conditions in the ACL statement. Note:
27 this is just like $address_data. The value does not persist after the end
28 of the current ACL statement. If you want to preserve it, you can use one
29 of the ACL variables.
31 5. The redirect router has two new options: forbid_sieve_filter and
32 forbid_exim_filter. When filtering is enabled by allow_filter, these
33 options control which type(s) of filtering are permitted. By default, both
34 Exim and Sieve filters are allowed.
36 6. A new option for callouts makes it possible to set a different (usually
37 smaller) timeout for making the SMTP connection. The keyword is "connect".
38 For example:
40 verify = sender/callout=5s,connect=1s
42 If not specified, it defaults to the general timeout value.
35edf2ff 44
45Version 4.43
48 1. There is a new Boolean global option called mua_wrapper, defaulting false.
49 This causes Exim to run an a restricted mode, in order to provide a very
50 specific service.
52 Background: On a personal computer, it is a common requirement for all
53 email to be sent to a smarthost. There are plenty of MUAs that can be
54 configured to operate that way, for all the popular operating systems.
55 However, there are MUAs for Unix-like systems that cannot be so configured:
56 they submit messages using the command line interface of
57 /usr/sbin/sendmail. In addition, utility programs such as cron submit
58 messages this way.
60 Requirement: The requirement is for something that can provide the
61 /usr/sbin/sendmail interface and deliver messages to a smarthost, but not
62 provide any queueing or retrying facilities. Furthermore, the delivery to
63 the smarthost should be synchronous, so that if it fails, the sending MUA
64 is immediately informed. In other words, we want something that in effect
65 converts a command-line MUA into a TCP/SMTP MUA.
67 Solutions: There are a number of applications (for example, ssmtp) that do
68 this job. However, people have found them to be lacking in various ways.
69 For instance, some sites want to allow aliasing and forwarding before
70 sending to the smarthost.
72 Using Exim: Exim already had the necessary infrastructure for doing this
73 job. Just a few tweaks were needed to make it behave as required, though it
74 is somewhat of an overkill to use a fully-featured MTA for this purpose.
76 Setting mua_wrapper=true causes Exim to run in a special mode where it
77 assumes that it is being used to "wrap" a command-line MUA in the manner
78 just described.
80 If you set mua_wrapper=true, you also need to provide a compatible router
81 and transport configuration. Typically there will be just one router and
82 one transport, sending everything to a smarthost.
84 When run in MUA wrapping mode, the behaviour of Exim changes in the
85 following ways:
87 (a) A daemon cannot be run, nor will Exim accept incoming messages from
88 inetd. In other words, the only way to submit messages is via the
89 command line.
91 (b) Each message is synchonously delivered as soon as it is received (-odi
92 is assumed). All queueing options (queue_only, queue_smtp_domains,
93 control=queue, control=freeze in an ACL etc.) are quietly ignored. The
94 Exim reception process does not finish until the delivery attempt is
95 complete. If the delivery was successful, a zero return code is given.
97 (c) Address redirection is permitted, but the final routing for all
98 addresses must be to the same remote transport, and to the same list of
99 hosts. Furthermore, the return_address must be the same for all
100 recipients, as must any added or deleted header lines. In other words,
101 it must be possible to deliver the message in a single SMTP
102 transaction, however many recipients there are.
104 (d) If the conditions in (c) are not met, or if routing any address results
105 in a failure or defer status, or if Exim is unable to deliver all the
106 recipients successfully to one of the hosts immediately, delivery of
107 the entire message fails.
109 (e) Because no queueing is allowed, all failures are treated as permanent;
110 there is no distinction between 4xx and 5xx SMTP response codes from
111 the smarthost. Furthermore, because only a single yes/no response can
112 be given to the caller, it is not possible to deliver to some
113 recipients and not others. If there is an error (temporary or
114 permanent) for any recipient, all are failed.
116 (f) If more than one host is listed, Exim will try another host after a
117 connection failure or a timeout, in the normal way. However, if this
118 kind of failure happens for all the hosts, the delivery fails.
120 (g) When delivery fails, an error message is written to the standard error
121 stream (as well as to Exim's log), and Exim exits to the caller with a
122 return code value 1. The message is expunged from Exim's spool files.
123 No bounce messages are ever generated.
125 (h) No retry data is maintained, and any retry rules are ignored.
127 (i) A number of Exim options are overridden: deliver_drop_privilege is
128 forced true, max_rcpt in the smtp transport is forced to "unlimited",
129 remote_max_parallel is forced to one, and fallback hosts are ignored.
131 The overall effect is that Exim makes a single synchronous attempt to
132 deliver the message, failing if there is any kind of problem. Because no
133 local deliveries are done and no daemon can be run, Exim does not need root
134 privilege. It should be possible to run it setuid=exim instead of
135 setuid=root. See section 48.3 in the 4.40 manual for a general discussion
136 about the advantages and disadvantages of running without root privilege.
138 2. There have been problems with DNS servers when SRV records are looked up.
139 Some mis-behaving servers return a DNS error or timeout when a non-existent
140 SRV record is sought. Similar problems have in the past been reported for
141 MX records. The global dns_again_means_nonexist option can help with this
142 problem, but it is heavy-handed because it is a global option. There are
143 now two new options for the dnslookup router. They are called
144 srv_fail_domains and mx_fail_domains. In each case, the value is a domain
145 list. If an attempt to look up an SRV or MX record results in a DNS failure
146 or "try again" response, and the domain matches the relevant list, Exim
147 behaves as if the DNS had responded "no such record". In the case of an SRV
148 lookup, this means that the router proceeds to look for MX records; in the
149 case of an MX lookup, it proceeds to look for A or AAAA records, unless the
150 domain matches mx_domains.
152 3. The following functions are now available in the local_scan() API:
154 (a) void header_remove(int occurrence, uschar *name)
156 This function removes header lines. If "occurrence" is zero or negative,
157 all occurrences of the header are removed. If occurrence is greater
158 than zero, that particular instance of the header is removed. If no
159 header(s) can be found that match the specification, the function does
160 nothing.
162 (b) BOOL header_testname(header_line *hdr, uschar *name, int length,
163 BOOL notdel)
165 This function tests whether the given header has the given name. It
166 is not just a string comparison, because whitespace is permitted
167 between the name and the colon. If the "notdel" argument is TRUE, a
168 FALSE return is forced for all "deleted" headers; otherwise they are
169 not treated specially. For example:
171 if (header_testname(h, US"X-Spam", 6, TRUE)) ...
173 (c) void header_add_at_position(BOOL after, uschar *name, BOOL topnot,
174 int type, char *format, ...)
176 This function adds a new header line at a specified point in the header
177 chain. If "name" is NULL, the new header is added at the end of the
178 chain if "after" is TRUE, or at the start if "after" is FALSE. If
179 "name" is not NULL, the headers are searched for the first non-deleted
180 header that matches the name. If one is found, the new header is added
181 before it if "after" is FALSE. If "after" is true, the new header is
182 added after the found header and any adjacent subsequent ones with the
183 same name (even if marked "deleted"). If no matching non-deleted header
184 is found, the "topnot" option controls where the header is added. If it
185 is TRUE, addition is at the top; otherwise at the bottom. Thus, to add
186 a header after all the Received: headers, or at the top if there are no
187 Received: headers, you could use
189 header_add_at_position(TRUE, US"Received", TRUE, ' ', "X-xxx: ...");
191 Normally, there is always at least one non-deleted Received: header,
192 but there may not be if received_header_text expands to an empty
193 string.
195 (d) BOOL receive_remove_recipient(uschar *recipient)
197 This is a convenience function to remove a named recipient from the
198 list of recipients. It returns TRUE if a recipient was removed, and
199 FALSE if no matching recipient could be found. The argument must be a
200 complete email address.
202 4. When an ACL "warn" statement adds one or more header lines to a message,
203 they are added at the end of the existing header lines by default. It is
204 now possible to specify that any particular header line should be added
205 right at the start (before all the Received: lines) or immediately after
206 the first block of Received: lines in the message. This is done by
207 specifying :at_start: or :after_received: (or, for completeness, :at_end:)
208 before the text of the header line. (Header text cannot start with a colon,
209 as there has to be a header name first.) For example:
211 warn message = :after_received:X-My-Header: something or other...
213 If more than one header is supplied in a single warn statement, each one is
214 treated independently and can therefore be placed differently. If you add
215 more than one line at the start, or after the Received: block, they will
216 end up in reverse order.
218 Warning: This facility currently applies only to header lines that are
219 added in an ACL. It does NOT work for header lines that are added in a
220 system filter or in a router or transport.
222 5. There is now a new error code that can be used in retry rules. Its name is
223 "rcpt_4xx", and there are three forms. A literal "rcpt_4xx" matches any 4xx
224 error received for an outgoing SMTP RCPT command; alternatively, either the
225 first or both of the x's can be given as digits, for example: "rcpt_45x" or
226 "rcpt_436". If you want (say) to recognize 452 errors given to RCPT
227 commands by a particular host, and have only a one-hour retry for them, you
228 can set up a retry rule of this form:
230 the.host.name rcpt_452 F,1h,10m
232 Naturally, this rule must come before any others that would match.
234 These new errors apply to both outgoing SMTP (the smtp transport) and
235 outgoing LMTP (either the lmtp transport, or the smtp transport in LMTP
236 mode). Note, however, that they apply only to responses to RCPT commands.
238 6. The "postmaster" option of the callout feature of address verification has
239 been extended to make it possible to use a non-empty MAIL FROM address when
240 checking a postmaster address. The new suboption is called "postmaster_
241 mailfrom", and you use it like this:
243 require verify = sender/callout=postmaster_mailfrom=abc@x.y.z
245 Providing this suboption causes the postmaster check to be done using the
246 given address. The original "postmaster" option is equivalent to
248 require verify = sender/callout=postmaster_mailfrom=
250 If both suboptions are present, the rightmost one overrides.
252 Important notes:
254 (1) If you use a non-empty sender address for postmaster checking, there is
255 the likelihood that the remote host will itself initiate a callout
256 check back to your host to check that address. As this is a "normal"
257 callout check, the sender will most probably be empty, thus avoiding
258 possible callout loops. However, to be on the safe side it would be
259 best to set up your own ACLs so that they do not do sender verification
260 checks when the recipient is the address you use for postmaster callout
261 checking.
263 (2) The caching arrangements for postmaster checking do NOT take account of
264 the sender address. It is assumed that either the empty address, or a
265 fixed non-empty address will be used. All that Exim remembers is that
266 the postmaster check for the domain succeeded or failed.
268 7. When verifying addresses in header lines using the verify=header_sender
269 option, Exim behaves by default as if the addresses are envelope sender
270 addresses from a message. Callout verification therefore tests to see
271 whether a bounce message could be delivered, by using an empty address in
272 the MAIL FROM command. However, it is arguable that these addresses might
273 never be used as envelope senders, and could therefore justifiably reject
274 bounce messages (empty senders). There is now an additional callout option
275 for verify=header_sender that allows you to specify what address to use in
276 the MAIL FROM command. You use it as in this example:
278 require verify = header_sender/callout=mailfrom=abcd@x.y.z
280 Important notes:
282 (1) As in the case of postmaster_mailfrom (see above), you should think
283 about possible loops.
285 (2) In this case, as in the case of recipient callouts with non-empty
286 senders (the use_sender option), caching is done on the basis of a
287 recipient/sender pair.
289 8. If you build Exim with USE_READLINE=yes in Local/Makefile, it will try to
290 load libreadline dynamically whenever the -be (test expansion) option is
291 used without command line arguments. If successful, it will then use
292 readline() for reading the test data. A line history is supported. By the
293 time Exim does this, it is running as the calling user, so this should not
294 cause any security problems. Security is the reason why this is NOT
295 supported for -bt or -bv, when Exim is running as root or exim,
296 respectively. Note that this option adds to the size of the Exim binary,
297 because the dynamic loading library is not otherwise included. On my
298 desktop it adds about 2.5K. You may need to add -ldl to EXTRA_LIBS when you
299 set USE_READLINE=yes.
301 9. Added ${str2b64:<string>} to the expansion operators. This operator
302 converts an arbitrary string into one that is base64 encoded.
30410. A new authenticator, called cyrus_sasl, has been added. This requires
305 the presence of the Cyrus SASL library; it authenticates by calling this
306 library, which supports a number of authentication mechanisms, including
307 PLAIN and LOGIN, but also several others that Exim does not support
308 directly. The code for this authenticator was provided by Matthew
309 Byng-Maddick of A L Digital Ltd (http://www.aldigital.co.uk). Here follows
310 draft documentation:
314 The cyrus_sasl authenticator provides server support for the Cyrus library
315 Implementation of the RFC 2222 "Simple Authentication and Security Layer".
316 It provides a gatewaying mechanism directly to the Cyrus interface, so if
317 your Cyrus library can do, for example, CRAM-MD5, then so can the
318 cyrus_sasl authenticator. By default it uses the public name of the driver
319 to determine which mechanism to support.
321 Where access to some kind of secret file is required, for example in GSSAPI
322 or CRAM-MD5, it is worth noting that the authenticator runs as the exim
323 user, and that the Cyrus SASL library has no way of escalating privileges
324 by default. You may also find you need to set environment variables,
325 depending on the driver you are using.
327 xx.1 Using cyrus_sasl as a server
329 The cyrus_sasl authenticator has four private options. It puts the username
330 (on a successful authentication) into $1.
332 server_hostname Type: string* Default: $primary_hostname
334 This option selects the hostname that is used when communicating with
335 the library. It is up to the underlying SASL plug-in what it does with
336 this data.
338 server_mech Type: string Default: public_name
340 This option selects the authentication mechanism this driver should
341 use. It allows you to use a different underlying mechanism from the
342 advertised name. For example:
344 sasl:
345 driver = cyrus_sasl
346 public_name = X-ANYTHING
347 server_mech = CRAM-MD5
348 server_set_id = $1
350 server_realm Type: string Default: unset
352 This is the SASL realm that the server is claiming to be in.
354 server_service Type: string Default: "smtp"
356 This is the SASL service that the server claims to implement.
358 For straigthforward cases, you do not need to set any of the
359 authenticator's private options. All you need to do is to specify an
360 appropriate mechanism as the public name. Thus, if you have a SASL library
361 that supports CRAM-MD5 and PLAIN, you might have two authenticators as
362 follows:
364 sasl_cram_md5:
365 driver = cyrus_sasl
366 public_name = CRAM-MD5
367 server_set_id = $1
369 sasl_plain:
370 driver = cyrus_sasl
371 public_name = PLAIN
372 server_set_id = $1
37411. There is a new global option called tls_on_connect_ports. Its value must be
375 a list of port numbers; the most common use is expected to be
377 tls_on_connect_ports = 465
379 Setting this option has the same effect as -tls-on-connect on the command
380 line, but only for the specified ports. It applies to all connections, both
381 via the daemon and via inetd. You still need to specify all the ports for
382 the daemon (using daemon_smtp_ports or local_interfaces or the -X command
383 line option) because this option does not add an extra port -- rather, it
384 specifies different behaviour on a port that is defined elsewhere. The
385 -tls-on-connect command line option overrides tls_on_connect_ports, and
386 forces tls-on-connect for all ports.
38812. There is a new ACL that is run when a DATA command is received, before the
389 data itself is received. The ACL is defined by acl_smtp_predata. (Compare
390 acl_smtp_data, which is run after the data has been received.)
391 This new ACL allows a negative response to be given to the DATA command
392 itself. Header lines added by MAIL or RCPT ACLs are not visible at this
393 time, but any that are defined here are visible when the acl_smtp_data ACL
394 is run.
39613. The "control=submission" ACL modifier has an option "/domain=xxx" which
397 specifies the domain to be used when creating From: or Sender: lines using
398 the authenticated id as a local part. If the option is supplied with an
399 empty domain, that is, just "/domain=", Exim assumes that the authenticated
400 id is a complete email address, and it uses it as is when creating From:
401 or Sender: lines.
40314. It is now possible to make retry rules that apply only when the failing
404 message has a specific sender. In particular, this can be used to define
405 retry rules that apply only to bounce messages. The syntax is to add a new
406 third item to a retry rule, of the form "senders=<address list>". The retry
407 timings themselves then become the fourth item. For example:
409 * * senders=: F,1h,30m
411 would match all bounce messages. If the address list contains white space,
412 it must be enclosed in quotes. For example:
414 a.domain timeout senders="x@b.dom : y@c.dom" G,8h,10m,1.5
416 When testing retry rules using -brt, you can supply a sender using the -f
417 command line option, like this:
419 exim -f "" -brt user@dom.ain
421 If you do not set -f with -brt, a retry rule that contains a senders list
422 will never be matched.
42415. Two new control modifiers have been added to ACLs: "control = enforce_sync"
425 and "control = no_enforce_sync". This makes it possible to be selective
426 about when SMTP synchronization is enforced. The global option
427 smtp_enforce_sync now specifies the default state of the switch. These
428 controls can appear in any ACL, but the most obvious place to put them is
429 in the ACL defined by acl_smtp_connect, which is run at the start of an
430 incoming SMTP connection, before the first synchronization check.
43216. Another two new control modifiers are "control = caseful_local_part" and
433 "control = caselower_local_part". These are permitted only in the ACL
434 specified by acl_smtp_rcpt (i.e. during RCPT processing). By default, the
435 contents of $local_part are lower cased before ACL processing.
436 After "control = caseful_local_part", any uppercase letters in the original
437 local part are restored in $local_part for the rest of the ACL, or until
438 "control = caselower_local_part" is encountered. However, this applies only
439 to local part handling that takes place directly in the ACL (for example,
440 as a key in lookups). If a "verify = recipient" test is obeyed, the
441 case-related handling of the local part during the verification is
442 controlled by the router configuration (see the caseful_local_part generic
443 router option).
445 This facility could be used, for example, to add a spam score to local
446 parts containing upper case letters. For example, using $acl_m4 to
447 accumulate the spam score:
449 warn control = caseful_local_part
450 set acl_m4 = ${eval:\
451 $acl_m4 + \
452 ${if match{$local_part}{[A-Z]}{1}{0}}\
453 }
454 control = caselower_local_part
456 Notice that we put back the lower cased version afterwards, assuming that
457 is what is wanted for subsequent tests.
45917. The option hosts_connection_nolog is provided so that certain hosts can be
460 excepted from logging when the +smtp_connection log selector is set. For
461 example, you might want not to log SMTP connections from local processes,
462 or from, or from your local LAN. The option is a host list with
463 an unset default. Because it is consulted in the main loop of the daemon,
464 you should strive to restrict its value to a short inline list of IP
465 addresses and networks. To disable logging SMTP connections from local
466 processes, you must create a host list with an empty item. For example:
468 hosts_connection_nolog = :
470 If the +smtp_connection log selector is not set, this option has no effect.
47218. There is now an acl called acl_smtp_quit, which is run for the QUIT
473 command. The outcome of the ACL does not affect the response code to QUIT,
474 which is always 221. Thus, the ACL does not in fact control any access.
475 For this reason, the only verbs that are permitted are "accept" and "warn".
477 The ACL can be used for tasks such as custom logging at the end of an SMTP
478 session. For example, you can use ACL variables in other ACLs to count
479 messages, recipients, etc., and log the totals at QUIT time using one or
480 more "logwrite" modifiers on a "warn" command.
482 You do not need to have a final "accept", but if you do, you can use a
483 "message" modifier to specify custom text that is sent as part of the 221
484 response.
486 This ACL is run only for a "normal" QUIT. For certain kinds of disastrous
487 failure (for example, failure to open a log file, or when Exim is bombing
488 out because it has detected an unrecoverable error), all SMTP commands
489 from the client are given temporary error responses until QUIT is received
490 or the connection is closed. In these special cases, the ACL is not run.
49219. The appendfile transport has two new options, mailbox_size and mailbox_
493 filecount. If either these options are set, it is expanded, and the result
494 is taken as the current size of the mailbox or the number of files in the
495 mailbox, respectively. This makes it possible to use some external means of
496 maintaining the data about the size of a mailbox for enforcing quota
497 limits. The result of expanding these option values must be a decimal
498 number, optionally followed by "K" or "M".
50020. It seems that there are broken clients in use that cannot handle multiline
501 SMTP responses. Can't people who implement these braindead programs read?
502 RFC 821 mentions multiline responses, and it is over 20 years old. They
503 must handle multiline responses for EHLO, or do they still use HELO?
504 Anyway, here is YAWFAB (yet another workaround for asinine brokenness).
505 There's a new ACL switch that can be set by
507 control = no_multiline_responses
509 If this is set, it suppresses multiline SMTP responses from ACL rejections.
510 One way of doing this would have been just to put out these responses as
511 one long line. However, RFC 2821 specifies a maximum of 512 bytes per
512 response ("use multiline responses for more" it says), and some of the
513 responses might get close to that. So I have implemented this by doing two
514 very easy things:
516 (1) Extra information that is normally output as part of a rejection
517 caused by sender verification failure is omitted. Only the final line
518 (typically "sender verification failed") is now sent.
520 (2) If a "message" modifier supplies a multiline response, only the first
521 line is output.
523 The setting of the switch can, of course, be made conditional on the
524 calling host.
52621. There is now support for the libradius library that comes with FreeBSD.
527 This is an alternative to the radiusclient library that Exim already
528 supports. To use the FreeBSD library, you need to set
532 in Local/Makefile, in addition to RADIUS_CONFIGURE_FILE, and you probably
533 also need -libradius in EXTRALIBS.
536Version 4.42
539 1. The "personal" filter test is brought up-to-date with recommendations from
540 the Sieve specification: (a) The list of non-personal From: addresses now
541 includes "listserv", "majordomo", and "*-request"; (b) If the message
542 contains any header line starting with "List=-" it is treated as
543 non-personal.
545 2. The Sieve functionality has been extended to support the "copy" and
546 "vacation" extensions, and comparison tests.
548 3. There is now an overall timeout for performing a callout verification. It
549 defaults to 4 times the callout timeout, which applies to individual SMTP
550 commands during the callout. The overall timeout applies when there is more
551 than one host that can be tried. The timeout is checked before trying the
552 next host. This prevents very long delays if there are a large number of
553 hosts and all are timing out (e.g. when the network connections are timing
554 out). The value of the overall timeout can be changed by specifying an
555 additional sub-option for "callout", called "maxwait". For example:
557 verify = sender/callout=5s,maxwait=20s
559 4. Changes to the "personal" filter test:
561 (1) The list of non-personal local parts in From: addresses has been
562 extended to include "listserv", "majordomo", "*-request", and "owner-*",
563 taken from the Sieve specification recommendations.
565 (2) If the message contains any header line starting with "List-" it is
566 treated as non-personal.
568 (3) The test for "circular" in the Subject: header line has been removed
569 because it now seems ill-conceived.
571 5. The autoreply transport has a new option called never_mail. This is an
572 address list. If any run of the transport creates a message with a
573 recipient that matches any item in the list, that recipient is quietly
574 discarded. If all recipients are discarded, no message is created.
577Version 4.40
580The documentation is up-to-date for the 4.40 release. What follows here is a
581brief list of the new features that have been added since 4.30.
583 1. log_incoming_interface affects more log lines.
585 2. New ACL modifier "control = submission".
587 3. CONFIGURE_OWNER can be set at build time to define an alternative owner for
588 the configuration file, in addition to root and exim.
590 4. Added expansion variables $body_zerocount, $recipient_data, and
591 $sender_data.
593 5. The time of last modification of the "new" subdirectory is now used as the
594 "mailbox time last read" when there is a quota error for a maildir
595 delivery.
597 6. The special item "+ignore_unknown" may now appear in host lists.
599 7. The special domain-matching patterns @mx_any, @mx_primary, and
600 @mx_secondary can now be followed by "/ignore=<ip list>".
602 8. New expansion conditions: match_domain, match_address, match_local_part,
603 lt, lti, le, lei, gt, gti, ge, and new expansion operators time_interval,
604 eval10, and base62d.
606 9. New lookup type called "iplsearch".
60810. New log selectors ident_timeout, tls_certificate_verified, queue_time,
609 deliver_time, outgoing_port, return_path_on_delivery.
61111. New global options smtp_active_hostname and tls_require_ciphers.
61312. Exinext has -C and -D options.
61513. "domainlist_cache" forces caching of an apparently variable list.
61714. For compatibility with Sendmail, the command line option -prval:sval
618 is equivalent to -oMr rval -oMs sval.
62015. New callout options use_sender and use_postmaster for use when verifying
621 recipients.
62316. John Jetmore's "exipick" utility has been added to the distribution.
62517. The TLS code now supports CRLs.
62718. The dnslookup router and the dnsdb lookup type now support the use of SRV
628 records.
63019. The redirect router has a new option called qualify_domain.
63220. exigrep's output now also includes lines that are not related to any
633 particular message, but which do match the pattern.
63521. New global option write_rejectlog. If it is set false, Exim no longer
636 writes anything to the reject log.