4 This file contains descriptions of new features that have been added to Exim.
5 Before a formal release, there may be quite a lot of detail so that people can
6 test from the snapshots or the Git before the documentation is updated. Once
7 the documentation is updated, this file is reduced to a short list.
12 1. EXPERIMENTAL_SRS_NATIVE optional build feature. See the experimental.spec
15 2. Channel-binding for authenticators is now supported under OpenSSL.
16 Previously it was GnuTLS-only.
20 4. Client-side support in the gsasl authenticator. Tested against the
21 plaintext driver for PLAIN; only against itself for SCRAM-SHA-1 and
22 SCRAM-SHA-1-PLUS methods.
24 5. Server-side support in the gsasl authenticator for encrypted passwords, as
25 an alternate for the existing plaintext.
27 6. Variable $local_part_data now also set by router check_local_user option,
28 with an de-tainted version of $local_part.
30 7. Named-list definitions can now be prefixed "hide" so that "-bP" commands do
31 not output the content. Previously this could only be done on options.
33 8. As an exerimental feature, the dovecot authenticatino driver supports inet
34 sockets. Previously it was unix-domain sockets only.
36 9. The ACL control "queue_only" can also be spelled "queue", and now takes an
37 option "first_pass_route" to do the same as a "-odqs" on the command line.
39 10. Items specified for the router and transport headers_remove option can use
40 a trailing asterisk to specify globbing.
42 11. New $queue_size variable.
44 12. New variables $local_part_{pre,suf}fix_v.
46 13. New main option "sqlite_dbfile", for use in preference to prefixing the
47 lookup string. The older method fails when tainted variables are used
48 in the lookup, as the filename becomes tainted. The new method keeps the
51 14. Options on the dsearch lookup, to return the full path and to filter
52 filetypes for matching.
54 15. Options on pgsql and mysql lookups, to specify server separate from the
57 16. Expansion item ${listquote {<char} {<item>}}.
59 17. An option for the ${readsocket {}{}{}} expansion to make the result data
62 18. dkim_verify_min_keysizes, a list of minimum acceptable public-key sizes.
64 19. bounce_message_file and warn_message_file are now expanded before use.
66 20. $domain_data and $localpart_data are now set by all list-match successes.
67 Previously only list items that performed lookups did so.
68 Also, matching list items that are tail-match or RE-match now set the
69 numeric variables $0 (etc) in the same way os other RE matches.
76 1. An "external" authenticator, per RFC 4422 Appendix A.
78 2. A JSON lookup type, and JSON variants of the forall/any expansion conditions.
80 3. Variables $tls_in_cipher_std, $tls_out_cipher_std giving the RFC names
83 4. Log_selectors "msg_id" (on by default) and "msg_id_created".
85 5. A case_insensitive option for verify=not_blind.
87 6. EXPERIMENTAL_TLS_RESUME optional build feature. See the experimental.spec
90 7. A main option exim_version to override the version Exim
91 reports in verious places ($exim_version, $version_number).
93 8. Expansion operator ${sha2_N:} for N=256, 384, 512.
95 9. Router variables, $r_... settable from router options and usable in routers
98 10. The spf lookup now supports IPv6.
100 11. Main options for DKIM verify to filter hash and key types.
102 12. With TLS1.3, support for full-chain OCSP stapling.
104 13. Dual-certificate stacks on servers now support OCSP stapling, under OpenSSL.
106 14: An smtp:ehlo transport event, for observability of the remote offered features.
108 15: Support under OpenSSL for writing NSS-style key files for packet-capture
109 decode. The environment variable SSLKEYLOGFILE is used; if an absolute path
110 it must indicate a file under the spool directory; if relative the the spool
111 directory is prepended. Works on the server side only. Support under
112 GnuTLS was already there, being done purely by the library (server side
113 only, and exim must be run as root).
115 16: Command-line option to move messages from one named queue to another.
117 17. Variables $tls_in_ver, $tls_out_ver.
123 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
124 list when there are multiple headers having a given name. This matters
125 when individual headers are wrapped onto multiple lines; with previous
126 facilities hard to parse.
128 2. The ${readsocket } expansion item now takes a "tls" option, doing the
131 3. EXPERIMENTAL_REQUIRETLS and EXPERIMENTAL_PIPE_CONNECT optional build
132 features. See the experimental.spec file.
134 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
136 5. A "pipelining" log_selector.
138 6. Builtin macros for supported log_selector and openssl_options values.
140 7. JSON variants of the ${extract } expansion item.
142 8. A "noutf8" debug option, for disabling the UTF-8 characters in debug output.
144 9. TCP Fast Open support on MacOS.
149 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
150 version 3.5.6 or later.
152 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
153 OpenSSL versions are moved to mainline support from Experimental.
154 New SMTP transport option "dane_require_tls_ciphers".
156 3. Feature macros for the compiled-in set of malware scanner interfaces.
158 4. SPF support is promoted from Experimental to mainline status. The template
159 src/EDITME makefile does not enable its inclusion.
161 5. Logging control for DKIM verification. The existing DKIM log line is
162 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
163 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
164 a "dkim" log_selector.
166 6. Receive duration on <= lines, under a new log_selector "receive_time".
168 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
169 routing rules in the manualroute router.
171 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
172 under OpenSSL version 1.1.1 or later.
174 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
175 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
177 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
180 11. "exim -bP macro <name>" returns caller-usable status.
182 12. Expansion item ${authresults {<machine>}} for creating an
183 Authentication-Results: header.
185 13. EXPERIMENTAL_ARC. See the experimental.spec file.
186 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
188 14: A dane:fail event, intended to facilitate reporting.
190 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
191 contain all the servers in the cluster, all of which must be reachable from
192 the running exim instance. If the cluster has master/slave replication, the
193 list must contain all the master and slave servers.
195 16. Add an option to the Avast scanner interface: "pass_unscanned". This
196 allows to treat unscanned files as clean. Files may be unscanned for
197 several reasons: decompression bombs, broken archives.
203 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
204 wildcards will be expanded, values are collapsed.
206 2. The ${readsocket } expansion now takes an option to not shutdown the
207 connection after sending the query string. The default remains to do so.
209 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
210 deliveries on a single TCP connection can maintain a TLS connection
211 open. By default disabled for all hosts, doing so saves the cost of
212 making new TLS sessions, at the cost of having to proxy the data via
213 another process. Logging is also affected.
215 4. A malware connection type for the FPSCAND protocol.
217 5. An option for recipient verify callouts to hold the connection open for
218 further recipients and for delivery.
220 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
223 7. Optionally, an alternate format for spool data-files which matches the
224 wire format - meaning more efficient reception and transmission (at the
225 cost of difficulty with standard Unix tools). Only used for messages
226 received using the ESMTP CHUNKING option, and when a new main-section
227 option "spool_wireformat" (false by default) is set.
229 8. New main configuration option "commandline_checks_require_admin" to
230 restrict who can use various introspection options.
232 9. New option modifier "no_check" for quota and quota_filecount
233 appendfile transport.
235 10. Variable $smtp_command_history returning a comma-sep list of recent
238 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
239 log elements QT, DT and D, and timstamps in debug output.
241 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
242 while still in SYN_RECV state; as a client logs when the connection
243 is opened with a TFO cookie.
245 13. DKIM support for multiple signing, by domain and/or key-selector.
246 DKIM support for multiple hashes, and for alternate-identity tags.
247 Builtin macro with default list of signed headers.
248 Better syntax for specifying oversigning.
249 The DKIM ACL can override verification status, and status is visible in
252 14. Exipick understands -C|--config for an alternative Exim
255 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
256 for ${readsocket } expansions, and for ClamAV.
258 16. The "-be" expansion test mode now supports macros. Macros are expanded
259 in test lines, and new macros can be defined.
261 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
267 1. Allow relative config file names for ".include"
269 2. A main-section config option "debug_store" to control the checks on
270 variable locations during store-reset. Normally false but can be enabled
271 when a memory corruption issue is suspected on a production system.
277 1. The new perl_taintmode option allows to run the embedded perl
278 interpreter in taint mode.
280 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
282 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
285 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
286 N can be 224, 256 (default), 384, 512.
287 With GnuTLS 3.5.0 or later, only.
289 5. Facility for named queues: A command-line argument can specify
290 the queue name for a queue operation, and an ACL modifier can set
291 the queue to be used for a message. A $queue_name variable gives
294 6. New expansion operators base32/base32d.
296 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
297 performance increase and network load decrease. Main config option
298 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
301 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
303 9. Expansion operator escape8bit, like escape but not touching newline etc..
305 10. Feature macros, generated from compile options. All start with "_HAVE_"
306 and go on with some roughly recognisable name. Driver macros, for
307 router, transport and authentication drivers; names starting with "_DRIVER_".
308 Option macros, for each configuration-file option; all start with "_OPT_".
309 Use the "-bP macros" command-line option to see what is present.
311 11. Integer values for options can take a "G" multiplier.
313 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
314 returns from the target back to the initiator, rather than spooling the
317 13. New built-in constants available for tls_dhparam and default changed.
319 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
320 out copies of the message spool files for use by 3rd-party scanners.
322 15. A new option on the smtp transport, hosts_try_fastopen. If the system
323 supports it (on Linux it must be enabled in the kernel by the sysadmin)
324 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
325 but it permits a peer that also supports the facility to send its SMTP
326 banner immediately after the SYN,ACK segment rather then waiting for
327 another ACK - so saving up to one roundtrip time. Because it requires
328 previous communication with the peer (we save a cookie from it) this
329 will only become active on frequently-contacted destinations.
331 16. A new syslog_pid option to suppress PID duplication in syslog lines.
337 1. The ACL conditions regex and mime_regex now capture substrings
338 into numeric variables $regex1 to 9, like the "match" expansion condition.
340 2. New $callout_address variable records the address used for a spam=,
341 malware= or verify= callout.
343 3. Transports now take a "max_parallel" option, to limit concurrency.
345 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
346 The latter expands to a 8-element colon-sep set of hex digits including
347 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
348 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
349 The former operator strips leading zeroes and collapses the longest
350 set of 0-groups to a double-colon.
352 5. New "-bP config" support, to dump the effective configuration.
354 6. New $dkim_key_length variable.
356 7. New base64d and base64 expansion items (the existing str2b64 being a
357 synonym of the latter). Add support in base64 for certificates.
359 8. New main configuration option "bounce_return_linesize_limit" to
360 avoid oversize bodies in bounces. The default value matches RFC
363 9. New $initial_cwd expansion variable.
369 1. Support for using the system standard CA bundle.
371 2. New expansion items $config_file, $config_dir, containing the file
372 and directory name of the main configuration file. Also $exim_version.
374 3. New "malware=" support for Avast.
376 4. New "spam=" variant option for Rspamd.
378 5. Assorted options on malware= and spam= scanners.
380 6. A command-line option to write a comment into the logfile.
382 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
383 be configured to make connections via socks5 proxies.
385 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
386 the transmission of UTF-8 envelope addresses.
388 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
389 used encoding of Maildir folder names.
391 10. A logging option for slow DNS lookups.
393 11. New ${env {<variable>}} expansion.
395 12. A non-SMTP authenticator using information from TLS client certificates.
397 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
398 Patch originally by Wolfgang Breyha.
400 14. Main option "dns_trust_aa" for trusting your local nameserver at the
401 same level as DNSSEC.
406 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
407 DANE SMTP draft to assess a secure chain of trust of the certificate
408 used to establish the TLS connection based on a TLSA record in the
409 domain of the sender.
411 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
412 and several new events have been created. The reason is because it has
413 been expanded beyond just firing events during the transport phase. Any
414 existing TPDA transport options will have to be rewritten to use a new
415 $event_name expansion variable in a condition. Refer to the
416 experimental-spec.txt for details and examples.
418 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
419 server certs used for TLS match the result of the MX lookup. It does
420 not use the same mechanism as DANE.
430 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
431 configured to expect an initial header from a proxy that will make the
432 actual external source IP:host be used in exim instead of the IP of the
433 proxy that is connecting to it.
435 2. New verify option header_names_ascii, which will check to make sure
436 there are no non-ASCII characters in header names. Exim itself handles
437 those non-ASCII characters, but downstream apps may not, so Exim can
438 detect and reject if those characters are present.
440 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
441 codepoints with valid ones.
443 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
444 command line and matching a regex against the return data for trigger
445 and a second regex to extract malware_name. The mail spoolfile name can
446 be included in the command line.
448 5. The smtp transport now supports options "tls_verify_hosts" and
449 "tls_try_verify_hosts". If either is set the certificate verification
450 is split from the encryption operation. The default remains that a failed
451 verification cancels the encryption.
453 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
454 lookup can now set a list of servers to use that is different from the
457 7. New command-line option -C for exiqgrep to specify alternate exim.conf
458 file when searching the queue.
460 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
462 9. Support for DNSSEC on outbound connections.
464 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
465 "certextract" to extract fields from them. Hash operators md5 and sha1
466 work over them for generating fingerprints, and a new sha256 operator
469 11. PRDR is now supported dy default.
471 12. OCSP stapling is now supported by default.
473 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
474 Delivery Status Notification messages in MIME format, and negotiate
475 DSN features per RFC 3461.
481 1. New command-line option -bI:sieve will list all supported sieve extensions
482 of this Exim build on standard output, one per line.
483 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
484 query this to establish the correct list to include in the protocol's
485 SIEVE capability line.
487 2. If the -n option is combined with the -bP option, then the name of an
488 emitted option is not output, only the value (if visible to you).
489 For instance, "exim -n -bP pid_file_path" should just emit a pathname
490 followed by a newline, and no other text.
492 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
493 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
494 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
495 acceptable for security. (Option accepted but ignored if using OpenSSL).
496 Defaults to 1024, the old value. May be lowered only to 512, or raised as
497 far as you like. Raising this may hinder TLS interoperability with other
498 sites and is not currently recommended. Lowering this will permit you to
499 establish a TLS session which is not as secure as you might like.
501 Unless you really know what you are doing, leave it alone.
503 4. If not built with DISABLE_DNSSEC, Exim now has the main option
504 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
505 to send the DO flag to your recursive resolver. If you have a recursive
506 resolver, which can set the Authenticated Data (AD) flag in results, Exim
507 can now detect this. Exim does not perform validation itself, instead
508 relying upon a trusted path to the resolver.
510 Current status: work-in-progress; $sender_host_dnssec variable added.
512 5. DSCP support for outbound connections: on a transport using the smtp driver,
513 set "dscp = ef", for instance, to cause the connections to have the relevant
514 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
516 Similarly for inbound connections, there is a new control modifier, dscp,
517 so "warn control = dscp/ef" in the connect ACL, or after authentication.
519 Supported values depend upon system libraries. "exim -bI:dscp" to list the
520 ones Exim knows of. You can also set a raw number 0..0x3F.
522 6. The -G command-line flag is no longer ignored; it is now equivalent to an
523 ACL setting "control = suppress_local_fixups". The -L command-line flag
524 is now accepted and forces use of syslog, with the provided tag as the
525 process name. A few other flags used by Sendmail are now accepted and
528 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
529 ACL modifier; works for single-recipient mails which are received on and
530 deliverable via SMTP. Using the connection made for a recipient verify,
531 if requested before the verify, or a new one made for the purpose while
532 the inbound connection is still active. The bulk of the mail item is copied
533 direct from the inbound socket to the outbound (as well as the spool file).
534 When the source notifies the end of data, the data acceptance by the destination
535 is negotiated before the acceptance is sent to the source. If the destination
536 does not accept the mail item, for example due to content-scanning, the item
537 is not accepted from the source and therefore there is no need to generate
538 a bounce mail. This is of benefit when providing a secondary-MX service.
539 The downside is that delays are under the control of the ultimate destination
542 The Received-by: header on items delivered by cutthrough is generated
543 early in reception rather than at the end; this will affect any timestamp
544 included. The log line showing delivery is recorded before that showing
545 reception; it uses a new ">>" tag instead of "=>".
547 To support the feature, verify-callout connections can now use ESMTP and TLS.
548 The usual smtp transport options are honoured, plus a (new, default everything)
549 hosts_verify_avoid_tls.
551 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
552 for specific access to the information for each connection. The old names
553 are present for now but deprecated.
555 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
557 8. New expansion operators ${listnamed:name} to get the content of a named list
558 and ${listcount:string} to count the items in a list.
560 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
561 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
562 modules. For some situations this is desirable, but we expect admin in
563 those situations to know they want the feature. More commonly, it means
564 that GUI user modules get loaded and are broken by the setuid Exim being
565 unable to access files specified in environment variables and passed
566 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
567 unless this new option is set.
569 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
570 so have also added a build option which can be used to build Exim with GnuTLS
571 but without trying to use any kind of PKCS11 support. Uncomment this in the
574 AVOID_GNUTLS_PKCS11=yes
576 10. The "acl = name" condition on an ACL now supports optional arguments.
577 New expansion item "${acl {name}{arg}...}" and expansion condition
578 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
579 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
580 Variable $acl_narg contains the number of arguments. If the ACL sets
581 a "message =" value this becomes the result of the expansion item,
582 or the value of $value for the expansion condition. If the ACL returns
583 accept the expansion condition is true; if reject, false. A defer
584 return results in a forced fail.
586 11. Routers and transports can now have multiple headers_add and headers_remove
587 option lines. The concatenated list is used.
589 12. New ACL modifier "remove_header" can remove headers before message gets
590 handled by routers/transports.
592 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
593 "aaaa" and "a" lookups is done and the full set of results returned.
595 14. New expansion variable $headers_added with content from ACL add_header
596 modifier (but not yet added to message).
598 15. New 8bitmime status logging option for received messages. Log field "M8S".
600 16. New authenticated_sender logging option, adding to log field "A".
602 17. New expansion variables $router_name and $transport_name. Useful
603 particularly for debug_print as -bt command-line option does not
604 require privilege whereas -d does.
606 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
607 proposed extension to SMTP from Eric Hall.
609 19. The pipe transport has gained the force_command option, to allow
610 decorating commands from user .forward pipe aliases with prefix
611 wrappers, for instance.
613 20. Callout connections can now AUTH; the same controls as normal delivery
616 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
617 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
618 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
619 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
620 dmarc_status. It adds new control flags dmarc_disable_verify and
621 dmarc_enable_forensic. The default for the dmarc_tld_file option is
622 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
624 22. Add expansion variable $authenticated_fail_id, which is the username
625 provided to the authentication method which failed. It is available
626 for use in subsequent ACL processing (typically quit or notquit ACLs).
628 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
631 24. New ${hexquote:..string..} expansion operator converts non-printable
632 characters in the string to \xNN form.
634 25. Experimental TPDA (Transport Post Delivery Action) function added.
635 Patch provided by Axel Rau.
637 26. Experimental Redis lookup added. Patch provided by Warren Baker.
643 1. New authenticator driver, "gsasl". Server-only (at present).
644 This is a SASL interface, licensed under GPL, which can be found at
645 http://www.gnu.org/software/gsasl/.
646 This system does not provide sources of data for authentication, so
647 careful use needs to be made of the conditions in Exim.
649 2. New authenticator driver, "heimdal_gssapi". Server-only.
650 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
651 is no longer honoured for setuid programs by Heimdal. Use the
652 "server_keytab" option to point to the keytab.
654 3. The "pkg-config" system can now be used when building Exim to reference
655 cflags and library information for lookups and authenticators, rather
656 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
657 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
658 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
660 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
661 find the headers and libraries for PCRE.
663 4. New expansion variable $tls_bits.
665 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
666 be joined together with ASCII NUL characters to construct the key to pass
667 into the DBM library. Can be used with gsasl to access sasldb2 files as
670 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
672 Avoid release 1.0.1a if you can. Note that the default value of
673 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
674 increased susceptibility to attack. This may still have interoperability
675 implications for very old clients (see version 4.31 change 37) but
676 administrators can choose to make the trade-off themselves and restore
677 compatibility at the cost of session security.
679 7. Use of the new expansion variable $tls_sni in the main configuration option
680 tls_certificate will cause Exim to re-expand the option, if the client
681 sends the TLS Server Name Indication extension, to permit choosing a
682 different certificate; tls_privatekey will also be re-expanded. You must
683 still set these options to expand to valid files when $tls_sni is not set.
685 The SMTP Transport has gained the option tls_sni, which will set a hostname
686 for outbound TLS sessions, and set $tls_sni too.
688 A new log_selector, +tls_sni, has been added, to log received SNI values
689 for Exim as a server.
691 8. The existing "accept_8bitmime" option now defaults to true. This means
692 that Exim is deliberately not strictly RFC compliant. We're following
693 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
694 Those who disagree, or know that they are talking to mail servers that,
695 even today, are not 8-bit clean, need to turn off this option.
697 9. Exim can now be started with -bw (with an optional timeout, given as
698 -bw<timespec>). With this, stdin at startup is a socket that is
699 already listening for connections. This has a more modern name of
700 "socket activation", but forcing the activated socket to fd 0. We're
701 interested in adding more support for modern variants.
703 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
704 for numbers indicates multiplication by 1024^3.
706 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
707 gnutls_require_mac & gnutls_require_protocols are no longer supported.
708 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
709 string, documentation for which is at:
710 http://www.gnutls.org/manual/html_node/Priority-Strings.html
712 SNI support has been added to Exim's GnuTLS integration too.
714 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
715 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
717 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
718 is now available. If the contents of the file are valid, then Exim will
719 send that back in response to a TLS status request; this is OCSP Stapling.
720 Exim will not maintain the contents of the file in any way: administrators
721 are responsible for ensuring that it is up-to-date.
723 See "experimental-spec.txt" for more details.
725 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
726 identically to TXT record lookups.
728 14. New expansion variable $tod_epoch_l for higher-precision time.
730 15. New global option tls_dh_max_bits, defaulting to current value of NSS
731 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
732 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
734 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
735 Option can now be a path or an identifier for a standard prime.
736 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
737 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
740 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
741 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
742 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
748 1. New options for the ratelimit ACL condition: /count= and /unique=.
749 The /noupdate option has been replaced by a /readonly option.
751 2. The SMTP transport's protocol option may now be set to "smtps", to
752 use SSL-on-connect outbound.
754 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
755 there is a problem talking to the AV scanner, or the AV scanner running.
757 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
758 and check if the search item is a member of the list. This does not
759 support named lists, but does subject the list part to string expansion.
761 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
762 built, Exim no longer performs string expansion on the second string of
763 the match_* expansion conditions: "match_address", "match_domain",
764 "match_ip" & "match_local_part". Named lists can still be used.
770 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
771 or off in the resolver library.
777 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
778 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
779 libraries. The following global options have been added in support of
780 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
781 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
783 2. The pipe transport now takes a boolean option, "freeze_signal", default
784 false. When true, if the external delivery command exits on a signal then
785 Exim will freeze the message in the queue, instead of generating a bounce.
787 3. Log filenames may now use %M as an escape, instead of %D (still available).
788 The %M pattern expands to yyyymm, providing month-level resolution.
790 4. The $message_linecount variable is now updated for the maildir_tag option,
791 in the same way as $message_size, to reflect the real number of lines,
792 including any header additions or removals from transport.
794 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
795 Exim now selects entries randomly, to better scale in a cluster setup.
801 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
802 the flaw permitted the Exim run-time user to cause root to append to
803 arbitrary files of the attacker's choosing, with the content based
804 on content supplied by the attacker.
806 2. Exim now supports loading some lookup types at run-time, using your
807 platform's dlopen() functionality. This has limited platform support
808 and the intention is not to support every variant, it's limited to
809 dlopen(). This permits the main Exim binary to not be linked against
810 all the libraries needed for all the lookup types.
816 NOTE: this version is not guaranteed backwards-compatible, please read the
817 items below carefully
819 1. A new main configuration option, "openssl_options", is available if Exim
820 is built with SSL support provided by OpenSSL. The option allows
821 administrators to specify OpenSSL options to be used on connections;
822 typically this is to set bug compatibility features which the OpenSSL
823 developers have not enabled by default. There may be security
824 consequences for certain options, so these should not be changed
827 2. A new pipe transport option, "permit_coredumps", may help with problem
828 diagnosis in some scenarios. Note that Exim is typically installed as
829 a setuid binary, which on most OSes will inhibit coredumps by default,
830 so that safety mechanism would have to be overridden for this option to
831 be able to take effect.
833 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
834 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
835 Note that this switches Exim to use a new API ("INSTREAM") and a future
836 release of ClamAV will remove support for the old API ("STREAM").
838 The av_scanner option, when set to "clamd", now takes an optional third
839 part, "local", which causes Exim to pass a filename to ClamAV instead of
840 the file content. This is the same behaviour as when clamd is pointed at
841 a Unix-domain socket. For example:
843 av_scanner = clamd:192.0.2.3 1234:local
845 ClamAV's ExtendedDetectionInfo response format is now handled.
847 4. There is now a -bmalware option, restricted to admin users. This option
848 takes one parameter, a filename, and scans that file with Exim's
849 malware-scanning framework. This is intended purely as a debugging aid
850 to ensure that Exim's scanning is working, not to replace other tools.
851 Note that the ACL framework is not invoked, so if av_scanner references
852 ACL variables without a fallback then this will fail.
854 5. There is a new expansion operator, "reverse_ip", which will reverse IP
855 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
857 ${reverse_ip:192.0.2.4}
859 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
860 -> 3.0.2.0.0.0.0.c.d.c.b.a.1.0.0.0.9.0.0.0.2.4.c.0.8.b.d.0.1.0.0.2
862 6. There is a new ACL control called "debug", to enable debug logging.
863 This allows selective logging of certain incoming transactions within
864 production environments, with some care. It takes two options, "tag"
865 and "opts"; "tag" is included in the filename of the log and "opts"
866 is used as per the -d<options> command-line option. Examples, which
867 don't all make sense in all contexts:
870 control = debug/tag=.$sender_host_address
871 control = debug/opts=+expand+acl
872 control = debug/tag=.$message_exim_id/opts=+expand
874 7. It has always been implicit in the design and the documentation that
875 "the Exim user" is not root. src/EDITME said that using root was
876 "very strongly discouraged". This is not enough to keep people from
877 shooting themselves in the foot in days when many don't configure Exim
878 themselves but via package build managers. The security consequences of
879 running various bits of network code are severe if there should be bugs in
880 them. As such, the Exim user may no longer be root. If configured
881 statically, Exim will refuse to build. If configured as ref:user then Exim
882 will exit shortly after start-up. If you must shoot yourself in the foot,
883 then henceforth you will have to maintain your own local patches to strip
886 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
887 condition logic to determine truth/failure and will fail to expand many
888 strings, bool_lax{} uses the router condition logic, where most strings
890 Note: bool{00} is false, bool_lax{00} is true.
892 9. Routers now support multiple "condition" tests.
894 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
895 Setting this allows an admin to define which entry in the tcpwrappers
896 config file will be used to control access to the daemon. This option
897 is only available when Exim is built with USE_TCP_WRAPPERS. The
898 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
901 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
902 the Exim run-time user, instead of root.
904 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
905 is forced on. This is mitigated by the new build option
906 TRUSTED_CONFIG_LIST which defines a list of configuration files which
907 are trusted; one per line. If a config file is owned by root and matches
908 a pathname in the list, then it may be invoked by the Exim build-time
909 user without Exim relinquishing root privileges.
911 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
912 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
913 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
914 include the main config. As a transition mechanism, we are temporarily
915 providing a work-around: the new build option WHITELIST_D_MACROS provides
916 a colon-separated list of macro names which may be overridden by the Exim
917 run-time user. The values of these macros are constrained to the regex
918 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
924 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
925 writable, the other to locking of MBX folders (not mbox).
927 2. MySQL stored procedures are now supported.
929 3. The dkim_domain transport option is now a list, not a single string, and
930 messages will be signed for each element in the list (discarding
933 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
934 in the presence of multiple character strings within the RR. Prior to 4.70,
935 only the first string would be returned. The dnsdb lookup now, by default,
936 preserves the pre-4.70 semantics, but also now takes an extended output
937 separator specification. The separator can be followed by a semicolon, to
938 concatenate the individual text strings together with no join character,
939 or by a comma and a second separator character, in which case the text
940 strings within a TXT record are joined on that second character.
941 Administrators are reminded that DNS provides no ordering guarantees
942 between multiple records in an RRset. For example:
944 foo.example. IN TXT "a" "b" "c"
945 foo.example. IN TXT "d" "e" "f"
947 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
948 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
949 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
955 1. Native DKIM support without an external library.
956 (Note that if no action to prevent it is taken, a straight upgrade will
957 result in DKIM verification of all signed incoming emails. See spec
958 for details on conditionally disabling)
960 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
962 3. There is now a bool{} expansion condition which maps certain strings to
963 true/false condition values (most likely of use in conjunction with the
964 and{} expansion operator).
966 4. The $spam_score, $spam_bar and $spam_report variables are now available
969 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
970 options, provided that Exim is invoked by an admin_user.
972 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
973 which increases compatibility with older clients at the cost of decreased
974 security. Don't set this unless you need to support such clients.
976 7. There is a new expansion operator, ${randint:...} which will produce a
977 "random" number less than the supplied integer. This randomness is
978 not guaranteed to be cryptographically strong, but depending upon how
979 Exim was built may be better than the most naive schemes.
981 8. Exim now explicitly ensures that SHA256 is available when linked against
984 9. The transport_filter_timeout option now applies to SMTP transports too.
990 1. Preliminary DKIM support in Experimental.
996 1. The body_linecount and body_zerocount C variables are now exported in the
999 2. When a dnslists lookup succeeds, the key that was looked up is now placed
1000 in $dnslist_matched. When the key is an IP address, it is not reversed in
1001 this variable (though it is, of course, in the actual lookup). In simple
1004 deny dnslists = spamhaus.example
1006 the key is also available in another variable (in this case,
1007 $sender_host_address). In more complicated cases, however, this is not
1008 true. For example, using a data lookup might generate a dnslists lookup
1011 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
1013 If this condition succeeds, the value in $dnslist_matched might be
1014 192.168.6.7 (for example).
1016 3. Authenticators now have a client_condition option. When Exim is running as
1017 a client, it skips an authenticator whose client_condition expansion yields
1018 "0", "no", or "false". This can be used, for example, to skip plain text
1019 authenticators when the connection is not encrypted by a setting such as:
1021 client_condition = ${if !eq{$tls_cipher}{}}
1023 Note that the 4.67 documentation states that $tls_cipher contains the
1024 cipher used for incoming messages. In fact, during SMTP delivery, it
1025 contains the cipher used for the delivery. The same is true for
1028 4. There is now a -Mvc <message-id> option, which outputs a copy of the
1029 message to the standard output, in RFC 2822 format. The option can be used
1030 only by an admin user.
1032 5. There is now a /noupdate option for the ratelimit ACL condition. It
1033 computes the rate and checks the limit as normal, but it does not update
1034 the saved data. This means that, in relevant ACLs, it is possible to lookup
1035 the existence of a specified (or auto-generated) ratelimit key without
1036 incrementing the ratelimit counter for that key.
1038 In order for this to be useful, another ACL entry must set the rate
1039 for the same key somewhere (otherwise it will always be zero).
1044 # Read the rate; if it doesn't exist or is below the maximum
1045 # we update it below
1046 deny ratelimit = 100 / 5m / strict / noupdate
1047 log_message = RATE: $sender_rate / $sender_rate_period \
1048 (max $sender_rate_limit)
1050 [... some other logic and tests...]
1052 warn ratelimit = 100 / 5m / strict / per_cmd
1053 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
1054 (max $sender_rate_limit)
1055 condition = ${if le{$sender_rate}{$sender_rate_limit}}
1059 6. The variable $max_received_linelength contains the number of bytes in the
1060 longest line that was received as part of the message, not counting the
1061 line termination character(s).
1063 7. Host lists can now include +ignore_defer and +include_defer, analogous to
1064 +ignore_unknown and +include_unknown. These options should be used with
1065 care, probably only in non-critical host lists such as whitelists.
1067 8. There's a new option called queue_only_load_latch, which defaults true.
1068 If set false when queue_only_load is greater than zero, Exim re-evaluates
1069 the load for each incoming message in an SMTP session. Otherwise, once one
1070 message is queued, the remainder are also.
1072 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
1073 cases when an SMTP session ends without sending QUIT. However, when Exim
1074 itself is is bad trouble, such as being unable to write to its log files,
1075 this ACL is not run, because it might try to do things (such as write to
1076 log files) that make the situation even worse.
1078 Like the QUIT ACL, this new ACL is provided to make it possible to gather
1079 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
1080 modifier is forbidden in this ACL.
1082 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
1083 to a string that indicates the reason for the termination of the SMTP
1084 connection. The possible values are:
1086 acl-drop Another ACL issued a "drop" command
1087 bad-commands Too many unknown or non-mail commands
1088 command-timeout Timeout while reading SMTP commands
1089 connection-lost The SMTP connection has been lost
1090 data-timeout Timeout while reading message data
1091 local-scan-error The local_scan() function crashed
1092 local-scan-timeout The local_scan() function timed out
1093 signal-exit SIGTERM or SIGINT
1094 synchronization-error SMTP synchronization error
1095 tls-failed TLS failed to start
1097 In most cases when an SMTP connection is closed without having received
1098 QUIT, Exim sends an SMTP response message before actually closing the
1099 connection. With the exception of acl-drop, the default message can be
1100 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
1101 "drop" verb in another ACL, it is the message from the other ACL that is
1104 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
1105 servers with individual queries. This is done by starting the query with
1106 "servers=x:y:z;", where each item in the list may take one of two forms:
1108 (1) If it is just a host name, the appropriate global option (mysql_servers
1109 or pgsql_servers) is searched for a host of the same name, and the
1110 remaining parameters (database, user, password) are taken from there.
1112 (2) If it contains any slashes, it is taken as a complete parameter set.
1114 The list of servers is used in exactly the same was as the global list.
1115 Once a connection to a server has happened and a query has been
1116 successfully executed, processing of the lookup ceases.
1118 This feature is intended for use in master/slave situations where updates
1119 are occurring, and one wants to update a master rather than a slave. If the
1120 masters are in the list for reading, you might have:
1122 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1124 In an updating lookup, you could then write
1126 ${lookup mysql{servers=master; UPDATE ...}
1128 If, on the other hand, the master is not to be used for reading lookups:
1130 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1132 you can still update the master by
1134 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1136 11. The message_body_newlines option (default FALSE, for backwards
1137 compatibility) can be used to control whether newlines are present in
1138 $message_body and $message_body_end. If it is FALSE, they are replaced by
1145 1. There is a new log selector called smtp_no_mail, which is not included in
1146 the default setting. When it is set, a line is written to the main log
1147 whenever an accepted SMTP connection terminates without having issued a
1150 2. When an item in a dnslists list is followed by = and & and a list of IP
1151 addresses, the behaviour was not clear when the lookup returned more than
1152 one IP address. This has been solved by the addition of == and =& for "all"
1153 rather than the default "any" matching.
1155 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1156 for the cipher algorithms. New options have been added to allow some of the
1157 other parameters to be varied.
1159 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1160 set, Exim compiles a runtime option called disable_fsync.
1162 5. There is a new variable called $smtp_count_at_connection_start.
1164 6. There's a new control called no_pipelining.
1166 7. There are two new variables called $sending_ip_address and $sending_port.
1167 These are set whenever an SMTP connection to another host has been set up.
1169 8. The expansion of the helo_data option in the smtp transport now happens
1170 after the connection to the server has been made.
1172 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1173 are encoded as per RFC 2047.
1175 10. There is a new log selector called "pid", which causes the current process
1176 id to be added to every log line, in square brackets, immediately after the
1179 11. Exim has been modified so that it flushes SMTP output before implementing
1180 a delay in an ACL. It also flushes the output before performing a callout,
1181 as this can take a substantial time. These behaviours can be disabled by
1182 obeying control = no_delay_flush or control = no_callout_flush,
1183 respectively, at some earlier stage of the connection.
1185 12. There are two new expansion conditions that iterate over a list. They are
1186 called forany and forall.
1188 13. There's a new global option called dsn_from that can be used to vary the
1189 contents of From: lines in bounces and other automatically generated
1190 messages ("delivery status notifications" - hence the name of the option).
1192 14. The smtp transport has a new option called hosts_avoid_pipelining.
1194 15. By default, exigrep does case-insensitive matches. There is now a -I option
1195 that makes it case-sensitive.
1197 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1198 been added to string expansions to make it easier to process lists of
1199 items, typically addresses.
1201 17. There's a new ACL modifier called "continue". It does nothing of itself,
1202 and processing of the ACL always continues with the next condition or
1203 modifier. It is provided so that the side effects of expanding its argument
1206 18. It is now possible to use newline and other control characters (those with
1207 values less than 32, plus DEL) as separators in lists.
1209 19. The exigrep utility now has a -v option, which inverts the matching
1212 20. The host_find_failed option in the manualroute router can now be set to
1219 No new features were added to 4.66.
1225 No new features were added to 4.65.
1231 1. ACL variables can now be given arbitrary names, as long as they start with
1232 "acl_c" or "acl_m" (for connection variables and message variables), are at
1233 least six characters long, with the sixth character being either a digit or
1236 2. There is a new ACL modifier called log_reject_target. It makes it possible
1237 to specify which logs are used for messages about ACL rejections.
1239 3. There is a new authenticator called "dovecot". This is an interface to the
1240 authentication facility of the Dovecot POP/IMAP server, which can support a
1241 number of authentication methods.
1243 4. The variable $message_headers_raw provides a concatenation of all the
1244 messages's headers without any decoding. This is in contrast to
1245 $message_headers, which does RFC2047 decoding on the header contents.
1247 5. In a DNS black list, if two domain names, comma-separated, are given, the
1248 second is used first to do an initial check, making use of any IP value
1249 restrictions that are set. If there is a match, the first domain is used,
1250 without any IP value restrictions, to get the TXT record.
1252 6. All authenticators now have a server_condition option.
1254 7. There is a new command-line option called -Mset. It is useful only in
1255 conjunction with -be (that is, when testing string expansions). It must be
1256 followed by a message id; Exim loads the given message from its spool
1257 before doing the expansions.
1259 8. Another similar new command-line option is called -bem. It operates like
1260 -be except that it must be followed by the name of a file that contains a
1263 9. When an address is delayed because of a 4xx response to a RCPT command, it
1264 is now the combination of sender and recipient that is delayed in
1265 subsequent queue runs until its retry time is reached.
1267 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1268 shift, have been added to the eval: and eval10: expansion items.
1270 11. The variables $interface_address and $interface_port have been renamed
1271 as $received_ip_address and $received_port, to make it clear that they
1272 relate to message reception rather than delivery. (The old names remain
1273 available for compatibility.)
1275 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1276 to vary the message that is sent when an SMTP command is accepted.
1282 1. There is a new Boolean option called filter_prepend_home for the redirect
1285 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1286 start of receiving a non-SMTP message, before any of the message has been
1289 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1290 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1291 start of the message for an SMTP error code.
1293 4. There is a new parameter for LDAP lookups called "referrals", which takes
1294 one of the settings "follow" (the default) or "nofollow".
1296 5. Version 20070721.2 of exipick now included, offering these new options:
1298 After all other sorting options have bee processed, reverse order
1299 before displaying messages (-R is synonym).
1301 Randomize order of matching messages before displaying.
1303 Instead of displaying the matching messages, display the sum
1305 --sort <variable>[,<variable>...]
1306 Before displaying matching messages, sort the messages according to
1307 each messages value for each variable.
1309 Negate the value for every test (returns inverse output from the
1310 same criteria without --not).
1316 1. The ${readsocket expansion item now supports Internet domain sockets as well
1317 as Unix domain sockets. If the first argument begins "inet:", it must be of
1318 the form "inet:host:port". The port is mandatory; it may be a number or the
1319 name of a TCP port in /etc/services. The host may be a name, or it may be an
1320 IP address. An ip address may optionally be enclosed in square brackets.
1321 This is best for IPv6 addresses. For example:
1323 ${readsocket{inet:[::1]:1234}{<request data>}...
1325 Only a single host name may be given, but if looking it up yield more than
1326 one IP address, they are each tried in turn until a connection is made. Once
1327 a connection has been made, the behaviour is as for ${readsocket with a Unix
1330 2. If a redirect router sets up file or pipe deliveries for more than one
1331 incoming address, and the relevant transport has batch_max set greater than
1332 one, a batch delivery now occurs.
1334 3. The appendfile transport has a new option called maildirfolder_create_regex.
1335 Its value is a regular expression. For a maildir delivery, this is matched
1336 against the maildir directory; if it matches, Exim ensures that a
1337 maildirfolder file is created alongside the new, cur, and tmp directories.
1343 The documentation is up-to-date for the 4.61 release. Major new features since
1344 the 4.60 release are:
1346 . An option called disable_ipv6, to disable the use of IPv6 completely.
1348 . An increase in the number of ACL variables to 20 of each type.
1350 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1351 $2, $3, (though those are still set) because the numeric variables get used
1352 for other things in complicated expansions.
1354 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1356 . It is possible to use setclassresources() on some BSD OS to control the
1357 resources used in pipe deliveries.
1359 . A new ACL modifier called add_header, which can be used with any verb.
1361 . More errors are detectable in retry rules.
1363 There are a number of other additions too.
1369 The documentation is up-to-date for the 4.60 release. Major new features since
1370 the 4.50 release are:
1372 . Support for SQLite.
1374 . Support for IGNOREQUOTA in LMTP.
1376 . Extensions to the "submission mode" features.
1378 . Support for Client SMTP Authorization (CSA).
1380 . Support for ratelimiting hosts and users.
1382 . New expansion items to help with the BATV "prvs" scheme.
1384 . A "match_ip" condition, that matches an IP address against a list.
1386 There are many more minor changes.