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. The expansion-test faciility (exim -be) can set variables.
14 2. An event on a failing SMTP AUTH, for both client and server operations.
16 3. Variable $sender_helo_verified with the result of an ACL "verify = helo".
18 4. Predefined macros for expansion items, operators, conditions and variables.
20 5. The smtp transport option "max_rcpt" is now expanded before use.
22 6. The tls_eccurve option for OpenSSL now takes a list of group names.
24 7. Queue runners for several queues can now be started from one daemon.
26 8. New utility exim_msgdate converts message-ids to human readable format.
28 9. An expansion operator for wrapping long header lines.
30 10. A commandline option to print just the message IDs of the queue
35 1. A new ACL condition: seen. Records/tests a timestamp against a key.
37 2. A variant of the "mask" expansion operator to give normalised IPv6.
39 3. UTC output option for exim_dumpdb, exim_fixdb.
41 4. An event for failing TLS connects to the daemon.
43 5. The ACL "debug" control gains options "stop", "pretrigger" and "trigger".
45 6. Query-style lookups are now checked for quoting, if the query string is
46 built using untrusted data ("tainted"). For now lack of quoting is merely
47 logged; a future release will upgrade this to an error.
49 7. The expansion conditions match_<list-type> and inlist now set $value for
50 the expansion of the "true" result of the ${if}. With a static list, this
51 can be used for de-tainting.
53 8. Recipient verify callouts now set $domain_data & $local_part_data, with
59 1. The fast-ramp two phase queue run support, previously experimental, is
60 now supported by default.
62 2. The native SRS support, previously experimental, is now supported. It is
63 not built unless specified in the Local/Makefile.
65 3. TLS resumption support, previously experimental, is now supported and
66 included in default builds.
68 4. Single-key LMDB lookups, previously experimental, are now supported.
69 The support is not built unless specified in the Local/Makefile.
71 5. Option "message_linelength_limit" on the smtp transport to enforce (by
72 default) the RFC 998 character limit.
74 6. An option to ignore the cache on a lookup.
76 7. Quota checking during reception (i.e. at SMTP time) for appendfile-
77 transport-managed quotas.
79 8. Sqlite lookups accept a "file=<path>" option to specify a per-operation
80 db file, replacing the previous prefix to the SQL string (which had
81 issues when the SQL used tainted values).
83 9. Lsearch lookups accept a "ret=full" option, to return both the portion
84 of the line matching the key, and the remainder.
86 10. A command-line option to have a daemon not create a notifier socket.
88 11. Faster TLS startup. When various configuration options contain no
89 expandable elements, the information can be preloaded and cached rather
90 than the previous behaviour of always loading at startup time for every
91 connection. This helps particularly for the CA bundle.
93 12. Proxy Protocol Timeout is configurable via "proxy_protocol_timeout"
96 13. Option "smtp_accept_max_per_connection" is now expanded.
98 14. Log selector "queue_time_exclusive", enabled by default, to exclude the
99 time taken for reception from QT log elements.
101 15. Main option "smtp_backlog_monitor", to set a level above which listen
102 socket backlogs are logged.
104 16. Main option "hosts_require_helo", requiring HELO or EHLO before MAIL.
106 17. A main config option "allow_insecure_tainted_data" allows to turn
108 18. TLS ALPN handling. By default, refuse TLS connections that try to specify
109 a non-smtp (eg. http) use. Options for customising.
111 19. Support for MacOS (darwin) has been dropped.
117 1. EXPERIMENTAL_SRS_NATIVE optional build feature. See the experimental.spec
120 2. Channel-binding for authenticators is now supported under OpenSSL.
121 Previously it was GnuTLS-only.
123 3. A msg:defer event.
125 4. Client-side support in the gsasl authenticator. Tested against the
126 plaintext driver for PLAIN; only against itself for SCRAM-SHA-1 and
127 SCRAM-SHA-1-PLUS methods.
129 5. Server-side support in the gsasl authenticator for encrypted passwords, as
130 an alternate for the existing plaintext.
132 6. Variable $local_part_data now also set by router check_local_user option,
133 with an de-tainted version of $local_part.
135 7. Named-list definitions can now be prefixed "hide" so that "-bP" commands do
136 not output the content. Previously this could only be done on options.
138 8. As an experimental feature, the dovecot authentication driver supports inet
139 sockets. Previously it was unix-domain sockets only.
141 9. The ACL control "queue_only" can also be spelled "queue", and now takes an
142 option "first_pass_route" to do the same as a "-odqs" on the command line.
144 10. Items specified for the router and transport headers_remove option can use
145 a trailing asterisk to specify globbing.
147 11. New $queue_size variable.
149 12. New variables $local_part_{pre,suf}fix_v.
151 13. New main option "sqlite_dbfile", for use in preference to prefixing the
152 lookup string. The older method fails when tainted variables are used
153 in the lookup, as the filename becomes tainted. The new method keeps the
156 14. Options on the dsearch lookup, to return the full path and to filter
157 filetypes for matching.
159 15. Options on pgsql and mysql lookups, to specify server separate from the
162 16. An option on all single-key lookups, to return (on a hit) a de-tainted
163 version of the lookup key rather than the looked-up data.
165 17. $domain_data and $local_part_data are now set by all list-match successes.
166 Previously only list items that performed lookups did so.
167 Also, matching list items that are tail-match or RE-match now set the
168 numeric variables $0 (etc) in the same way os other RE matches.
170 18. Expansion item ${listquote {<char} {<item>}}.
172 19. An option for the ${readsocket {}{}{}} expansion to make the result data
175 20. dkim_verify_min_keysizes, a list of minimum acceptable public-key sizes.
177 21. bounce_message_file and warn_message_file are now expanded before use.
179 22. New main config option spf_smtp_comment_template to customise the
180 $spf_smtp_comment variable
187 1. An "external" authenticator, per RFC 4422 Appendix A.
189 2. A JSON lookup type, and JSON variants of the forall/any expansion conditions.
191 3. Variables $tls_in_cipher_std, $tls_out_cipher_std giving the RFC names
194 4. Log_selectors "msg_id" (on by default) and "msg_id_created".
196 5. A case_insensitive option for verify=not_blind.
198 6. EXPERIMENTAL_TLS_RESUME optional build feature. See the experimental.spec
201 7. A main option exim_version to override the version Exim
202 reports in verious places ($exim_version, $version_number).
204 8. Expansion operator ${sha2_N:} for N=256, 384, 512.
206 9. Router variables, $r_... settable from router options and usable in routers
209 10. The spf lookup now supports IPv6.
211 11. Main options for DKIM verify to filter hash and key types.
213 12. With TLS1.3, support for full-chain OCSP stapling.
215 13. Dual-certificate stacks on servers now support OCSP stapling, under OpenSSL.
217 14: An smtp:ehlo transport event, for observability of the remote offered features.
219 15: Support under OpenSSL for writing NSS-style key files for packet-capture
220 decode. The environment variable SSLKEYLOGFILE is used; if an absolute path
221 it must indicate a file under the spool directory; if relative the the spool
222 directory is prepended. Works on the server side only. Support under
223 GnuTLS was already there, being done purely by the library (server side
224 only, and exim must be run as root).
226 16: Command-line option to move messages from one named queue to another.
228 17. Variables $tls_in_ver, $tls_out_ver.
234 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
235 list when there are multiple headers having a given name. This matters
236 when individual headers are wrapped onto multiple lines; with previous
237 facilities hard to parse.
239 2. The ${readsocket } expansion item now takes a "tls" option, doing the
242 3. EXPERIMENTAL_REQUIRETLS and EXPERIMENTAL_PIPE_CONNECT optional build
243 features. See the experimental.spec file.
245 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
247 5. A "pipelining" log_selector.
249 6. Builtin macros for supported log_selector and openssl_options values.
251 7. JSON variants of the ${extract } expansion item.
253 8. A "noutf8" debug option, for disabling the UTF-8 characters in debug output.
255 9. TCP Fast Open support on MacOS.
260 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
261 version 3.5.6 or later.
263 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
264 OpenSSL versions are moved to mainline support from Experimental.
265 New SMTP transport option "dane_require_tls_ciphers".
267 3. Feature macros for the compiled-in set of malware scanner interfaces.
269 4. SPF support is promoted from Experimental to mainline status. The template
270 src/EDITME makefile does not enable its inclusion.
272 5. Logging control for DKIM verification. The existing DKIM log line is
273 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
274 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
275 a "dkim" log_selector.
277 6. Receive duration on <= lines, under a new log_selector "receive_time".
279 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
280 routing rules in the manualroute router.
282 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
283 under OpenSSL version 1.1.1 or later.
285 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
286 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
288 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
291 11. "exim -bP macro <name>" returns caller-usable status.
293 12. Expansion item ${authresults {<machine>}} for creating an
294 Authentication-Results: header.
296 13. EXPERIMENTAL_ARC. See the experimental.spec file.
297 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
299 14: A dane:fail event, intended to facilitate reporting.
301 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
302 contain all the servers in the cluster, all of which must be reachable from
303 the running exim instance. If the cluster has master/slave replication, the
304 list must contain all the master and slave servers.
306 16. Add an option to the Avast scanner interface: "pass_unscanned". This
307 allows to treat unscanned files as clean. Files may be unscanned for
308 several reasons: decompression bombs, broken archives.
314 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
315 wildcards will be expanded, values are collapsed.
317 2. The ${readsocket } expansion now takes an option to not shutdown the
318 connection after sending the query string. The default remains to do so.
320 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
321 deliveries on a single TCP connection can maintain a TLS connection
322 open. By default disabled for all hosts, doing so saves the cost of
323 making new TLS sessions, at the cost of having to proxy the data via
324 another process. Logging is also affected.
326 4. A malware connection type for the FPSCAND protocol.
328 5. An option for recipient verify callouts to hold the connection open for
329 further recipients and for delivery.
331 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
334 7. Optionally, an alternate format for spool data-files which matches the
335 wire format - meaning more efficient reception and transmission (at the
336 cost of difficulty with standard Unix tools). Only used for messages
337 received using the ESMTP CHUNKING option, and when a new main-section
338 option "spool_wireformat" (false by default) is set.
340 8. New main configuration option "commandline_checks_require_admin" to
341 restrict who can use various introspection options.
343 9. New option modifier "no_check" for quota and quota_filecount
344 appendfile transport.
346 10. Variable $smtp_command_history returning a comma-sep list of recent
349 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
350 log elements QT, DT and D, and timstamps in debug output.
352 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
353 while still in SYN_RECV state; as a client logs when the connection
354 is opened with a TFO cookie.
356 13. DKIM support for multiple signing, by domain and/or key-selector.
357 DKIM support for multiple hashes, and for alternate-identity tags.
358 Builtin macro with default list of signed headers.
359 Better syntax for specifying oversigning.
360 The DKIM ACL can override verification status, and status is visible in
363 14. Exipick understands -C|--config for an alternative Exim
366 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
367 for ${readsocket } expansions, and for ClamAV.
369 16. The "-be" expansion test mode now supports macros. Macros are expanded
370 in test lines, and new macros can be defined.
372 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
378 1. Allow relative config file names for ".include"
380 2. A main-section config option "debug_store" to control the checks on
381 variable locations during store-reset. Normally false but can be enabled
382 when a memory corruption issue is suspected on a production system.
388 1. The new perl_taintmode option allows to run the embedded perl
389 interpreter in taint mode.
391 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
393 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
396 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
397 N can be 224, 256 (default), 384, 512.
398 With GnuTLS 3.5.0 or later, only.
400 5. Facility for named queues: A command-line argument can specify
401 the queue name for a queue operation, and an ACL modifier can set
402 the queue to be used for a message. A $queue_name variable gives
405 6. New expansion operators base32/base32d.
407 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
408 performance increase and network load decrease. Main config option
409 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
412 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
414 9. Expansion operator escape8bit, like escape but not touching newline etc..
416 10. Feature macros, generated from compile options. All start with "_HAVE_"
417 and go on with some roughly recognisable name. Driver macros, for
418 router, transport and authentication drivers; names starting with "_DRIVER_".
419 Option macros, for each configuration-file option; all start with "_OPT_".
420 Use the "-bP macros" command-line option to see what is present.
422 11. Integer values for options can take a "G" multiplier.
424 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
425 returns from the target back to the initiator, rather than spooling the
428 13. New built-in constants available for tls_dhparam and default changed.
430 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
431 out copies of the message spool files for use by 3rd-party scanners.
433 15. A new option on the smtp transport, hosts_try_fastopen. If the system
434 supports it (on Linux it must be enabled in the kernel by the sysadmin)
435 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
436 but it permits a peer that also supports the facility to send its SMTP
437 banner immediately after the SYN,ACK segment rather then waiting for
438 another ACK - so saving up to one roundtrip time. Because it requires
439 previous communication with the peer (we save a cookie from it) this
440 will only become active on frequently-contacted destinations.
442 16. A new syslog_pid option to suppress PID duplication in syslog lines.
448 1. The ACL conditions regex and mime_regex now capture substrings
449 into numeric variables $regex1 to 9, like the "match" expansion condition.
451 2. New $callout_address variable records the address used for a spam=,
452 malware= or verify= callout.
454 3. Transports now take a "max_parallel" option, to limit concurrency.
456 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
457 The latter expands to a 8-element colon-sep set of hex digits including
458 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
459 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
460 The former operator strips leading zeroes and collapses the longest
461 set of 0-groups to a double-colon.
463 5. New "-bP config" support, to dump the effective configuration.
465 6. New $dkim_key_length variable.
467 7. New base64d and base64 expansion items (the existing str2b64 being a
468 synonym of the latter). Add support in base64 for certificates.
470 8. New main configuration option "bounce_return_linesize_limit" to
471 avoid oversize bodies in bounces. The default value matches RFC
474 9. New $initial_cwd expansion variable.
480 1. Support for using the system standard CA bundle.
482 2. New expansion items $config_file, $config_dir, containing the file
483 and directory name of the main configuration file. Also $exim_version.
485 3. New "malware=" support for Avast.
487 4. New "spam=" variant option for Rspamd.
489 5. Assorted options on malware= and spam= scanners.
491 6. A command-line option to write a comment into the logfile.
493 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
494 be configured to make connections via socks5 proxies.
496 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
497 the transmission of UTF-8 envelope addresses.
499 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
500 used encoding of Maildir folder names.
502 10. A logging option for slow DNS lookups.
504 11. New ${env {<variable>}} expansion.
506 12. A non-SMTP authenticator using information from TLS client certificates.
508 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
509 Patch originally by Wolfgang Breyha.
511 14. Main option "dns_trust_aa" for trusting your local nameserver at the
512 same level as DNSSEC.
517 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
518 DANE SMTP draft to assess a secure chain of trust of the certificate
519 used to establish the TLS connection based on a TLSA record in the
520 domain of the sender.
522 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
523 and several new events have been created. The reason is because it has
524 been expanded beyond just firing events during the transport phase. Any
525 existing TPDA transport options will have to be rewritten to use a new
526 $event_name expansion variable in a condition. Refer to the
527 experimental-spec.txt for details and examples.
529 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
530 server certs used for TLS match the result of the MX lookup. It does
531 not use the same mechanism as DANE.
541 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
542 configured to expect an initial header from a proxy that will make the
543 actual external source IP:host be used in exim instead of the IP of the
544 proxy that is connecting to it.
546 2. New verify option header_names_ascii, which will check to make sure
547 there are no non-ASCII characters in header names. Exim itself handles
548 those non-ASCII characters, but downstream apps may not, so Exim can
549 detect and reject if those characters are present.
551 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
552 codepoints with valid ones.
554 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
555 command line and matching a regex against the return data for trigger
556 and a second regex to extract malware_name. The mail spoolfile name can
557 be included in the command line.
559 5. The smtp transport now supports options "tls_verify_hosts" and
560 "tls_try_verify_hosts". If either is set the certificate verification
561 is split from the encryption operation. The default remains that a failed
562 verification cancels the encryption.
564 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
565 lookup can now set a list of servers to use that is different from the
568 7. New command-line option -C for exiqgrep to specify alternate exim.conf
569 file when searching the queue.
571 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
573 9. Support for DNSSEC on outbound connections.
575 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
576 "certextract" to extract fields from them. Hash operators md5 and sha1
577 work over them for generating fingerprints, and a new sha256 operator
580 11. PRDR is now supported dy default.
582 12. OCSP stapling is now supported by default.
584 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
585 Delivery Status Notification messages in MIME format, and negotiate
586 DSN features per RFC 3461.
592 1. New command-line option -bI:sieve will list all supported sieve extensions
593 of this Exim build on standard output, one per line.
594 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
595 query this to establish the correct list to include in the protocol's
596 SIEVE capability line.
598 2. If the -n option is combined with the -bP option, then the name of an
599 emitted option is not output, only the value (if visible to you).
600 For instance, "exim -n -bP pid_file_path" should just emit a pathname
601 followed by a newline, and no other text.
603 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
604 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
605 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
606 acceptable for security. (Option accepted but ignored if using OpenSSL).
607 Defaults to 1024, the old value. May be lowered only to 512, or raised as
608 far as you like. Raising this may hinder TLS interoperability with other
609 sites and is not currently recommended. Lowering this will permit you to
610 establish a TLS session which is not as secure as you might like.
612 Unless you really know what you are doing, leave it alone.
614 4. If not built with DISABLE_DNSSEC, Exim now has the main option
615 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
616 to send the DO flag to your recursive resolver. If you have a recursive
617 resolver, which can set the Authenticated Data (AD) flag in results, Exim
618 can now detect this. Exim does not perform validation itself, instead
619 relying upon a trusted path to the resolver.
621 Current status: work-in-progress; $sender_host_dnssec variable added.
623 5. DSCP support for outbound connections: on a transport using the smtp driver,
624 set "dscp = ef", for instance, to cause the connections to have the relevant
625 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
627 Similarly for inbound connections, there is a new control modifier, dscp,
628 so "warn control = dscp/ef" in the connect ACL, or after authentication.
630 Supported values depend upon system libraries. "exim -bI:dscp" to list the
631 ones Exim knows of. You can also set a raw number 0..0x3F.
633 6. The -G command-line flag is no longer ignored; it is now equivalent to an
634 ACL setting "control = suppress_local_fixups". The -L command-line flag
635 is now accepted and forces use of syslog, with the provided tag as the
636 process name. A few other flags used by Sendmail are now accepted and
639 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
640 ACL modifier; works for single-recipient mails which are received on and
641 deliverable via SMTP. Using the connection made for a recipient verify,
642 if requested before the verify, or a new one made for the purpose while
643 the inbound connection is still active. The bulk of the mail item is copied
644 direct from the inbound socket to the outbound (as well as the spool file).
645 When the source notifies the end of data, the data acceptance by the destination
646 is negotiated before the acceptance is sent to the source. If the destination
647 does not accept the mail item, for example due to content-scanning, the item
648 is not accepted from the source and therefore there is no need to generate
649 a bounce mail. This is of benefit when providing a secondary-MX service.
650 The downside is that delays are under the control of the ultimate destination
653 The Received-by: header on items delivered by cutthrough is generated
654 early in reception rather than at the end; this will affect any timestamp
655 included. The log line showing delivery is recorded before that showing
656 reception; it uses a new ">>" tag instead of "=>".
658 To support the feature, verify-callout connections can now use ESMTP and TLS.
659 The usual smtp transport options are honoured, plus a (new, default everything)
660 hosts_verify_avoid_tls.
662 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
663 for specific access to the information for each connection. The old names
664 are present for now but deprecated.
666 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
668 8. New expansion operators ${listnamed:name} to get the content of a named list
669 and ${listcount:string} to count the items in a list.
671 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
672 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
673 modules. For some situations this is desirable, but we expect admin in
674 those situations to know they want the feature. More commonly, it means
675 that GUI user modules get loaded and are broken by the setuid Exim being
676 unable to access files specified in environment variables and passed
677 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
678 unless this new option is set.
680 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
681 so have also added a build option which can be used to build Exim with GnuTLS
682 but without trying to use any kind of PKCS11 support. Uncomment this in the
685 AVOID_GNUTLS_PKCS11=yes
687 10. The "acl = name" condition on an ACL now supports optional arguments.
688 New expansion item "${acl {name}{arg}...}" and expansion condition
689 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
690 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
691 Variable $acl_narg contains the number of arguments. If the ACL sets
692 a "message =" value this becomes the result of the expansion item,
693 or the value of $value for the expansion condition. If the ACL returns
694 accept the expansion condition is true; if reject, false. A defer
695 return results in a forced fail.
697 11. Routers and transports can now have multiple headers_add and headers_remove
698 option lines. The concatenated list is used.
700 12. New ACL modifier "remove_header" can remove headers before message gets
701 handled by routers/transports.
703 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
704 "aaaa" and "a" lookups is done and the full set of results returned.
706 14. New expansion variable $headers_added with content from ACL add_header
707 modifier (but not yet added to message).
709 15. New 8bitmime status logging option for received messages. Log field "M8S".
711 16. New authenticated_sender logging option, adding to log field "A".
713 17. New expansion variables $router_name and $transport_name. Useful
714 particularly for debug_print as -bt command-line option does not
715 require privilege whereas -d does.
717 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
718 proposed extension to SMTP from Eric Hall.
720 19. The pipe transport has gained the force_command option, to allow
721 decorating commands from user .forward pipe aliases with prefix
722 wrappers, for instance.
724 20. Callout connections can now AUTH; the same controls as normal delivery
727 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
728 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
729 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
730 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
731 dmarc_status. It adds new control flags dmarc_disable_verify and
732 dmarc_enable_forensic. The default for the dmarc_tld_file option is
733 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
735 22. Add expansion variable $authenticated_fail_id, which is the username
736 provided to the authentication method which failed. It is available
737 for use in subsequent ACL processing (typically quit or notquit ACLs).
739 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
742 24. New ${hexquote:..string..} expansion operator converts non-printable
743 characters in the string to \xNN form.
745 25. Experimental TPDA (Transport Post Delivery Action) function added.
746 Patch provided by Axel Rau.
748 26. Experimental Redis lookup added. Patch provided by Warren Baker.
754 1. New authenticator driver, "gsasl". Server-only (at present).
755 This is a SASL interface, licensed under GPL, which can be found at
756 http://www.gnu.org/software/gsasl/.
757 This system does not provide sources of data for authentication, so
758 careful use needs to be made of the conditions in Exim.
760 2. New authenticator driver, "heimdal_gssapi". Server-only.
761 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
762 is no longer honoured for setuid programs by Heimdal. Use the
763 "server_keytab" option to point to the keytab.
765 3. The "pkg-config" system can now be used when building Exim to reference
766 cflags and library information for lookups and authenticators, rather
767 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
768 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
769 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
771 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
772 find the headers and libraries for PCRE.
774 4. New expansion variable $tls_bits.
776 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
777 be joined together with ASCII NUL characters to construct the key to pass
778 into the DBM library. Can be used with gsasl to access sasldb2 files as
781 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
783 Avoid release 1.0.1a if you can. Note that the default value of
784 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
785 increased susceptibility to attack. This may still have interoperability
786 implications for very old clients (see version 4.31 change 37) but
787 administrators can choose to make the trade-off themselves and restore
788 compatibility at the cost of session security.
790 7. Use of the new expansion variable $tls_sni in the main configuration option
791 tls_certificate will cause Exim to re-expand the option, if the client
792 sends the TLS Server Name Indication extension, to permit choosing a
793 different certificate; tls_privatekey will also be re-expanded. You must
794 still set these options to expand to valid files when $tls_sni is not set.
796 The SMTP Transport has gained the option tls_sni, which will set a hostname
797 for outbound TLS sessions, and set $tls_sni too.
799 A new log_selector, +tls_sni, has been added, to log received SNI values
800 for Exim as a server.
802 8. The existing "accept_8bitmime" option now defaults to true. This means
803 that Exim is deliberately not strictly RFC compliant. We're following
804 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
805 Those who disagree, or know that they are talking to mail servers that,
806 even today, are not 8-bit clean, need to turn off this option.
808 9. Exim can now be started with -bw (with an optional timeout, given as
809 -bw<timespec>). With this, stdin at startup is a socket that is
810 already listening for connections. This has a more modern name of
811 "socket activation", but forcing the activated socket to fd 0. We're
812 interested in adding more support for modern variants.
814 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
815 for numbers indicates multiplication by 1024^3.
817 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
818 gnutls_require_mac & gnutls_require_protocols are no longer supported.
819 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
820 string, documentation for which is at:
821 http://www.gnutls.org/manual/html_node/Priority-Strings.html
823 SNI support has been added to Exim's GnuTLS integration too.
825 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
826 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
828 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
829 is now available. If the contents of the file are valid, then Exim will
830 send that back in response to a TLS status request; this is OCSP Stapling.
831 Exim will not maintain the contents of the file in any way: administrators
832 are responsible for ensuring that it is up-to-date.
834 See "experimental-spec.txt" for more details.
836 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
837 identically to TXT record lookups.
839 14. New expansion variable $tod_epoch_l for higher-precision time.
841 15. New global option tls_dh_max_bits, defaulting to current value of NSS
842 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
843 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
845 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
846 Option can now be a path or an identifier for a standard prime.
847 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
848 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
851 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
852 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
853 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
859 1. New options for the ratelimit ACL condition: /count= and /unique=.
860 The /noupdate option has been replaced by a /readonly option.
862 2. The SMTP transport's protocol option may now be set to "smtps", to
863 use SSL-on-connect outbound.
865 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
866 there is a problem talking to the AV scanner, or the AV scanner running.
868 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
869 and check if the search item is a member of the list. This does not
870 support named lists, but does subject the list part to string expansion.
872 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
873 built, Exim no longer performs string expansion on the second string of
874 the match_* expansion conditions: "match_address", "match_domain",
875 "match_ip" & "match_local_part". Named lists can still be used.
881 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
882 or off in the resolver library.
888 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
889 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
890 libraries. The following global options have been added in support of
891 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
892 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
894 2. The pipe transport now takes a boolean option, "freeze_signal", default
895 false. When true, if the external delivery command exits on a signal then
896 Exim will freeze the message in the queue, instead of generating a bounce.
898 3. Log filenames may now use %M as an escape, instead of %D (still available).
899 The %M pattern expands to yyyymm, providing month-level resolution.
901 4. The $message_linecount variable is now updated for the maildir_tag option,
902 in the same way as $message_size, to reflect the real number of lines,
903 including any header additions or removals from transport.
905 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
906 Exim now selects entries randomly, to better scale in a cluster setup.
912 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
913 the flaw permitted the Exim run-time user to cause root to append to
914 arbitrary files of the attacker's choosing, with the content based
915 on content supplied by the attacker.
917 2. Exim now supports loading some lookup types at run-time, using your
918 platform's dlopen() functionality. This has limited platform support
919 and the intention is not to support every variant, it's limited to
920 dlopen(). This permits the main Exim binary to not be linked against
921 all the libraries needed for all the lookup types.
927 NOTE: this version is not guaranteed backwards-compatible, please read the
928 items below carefully
930 1. A new main configuration option, "openssl_options", is available if Exim
931 is built with SSL support provided by OpenSSL. The option allows
932 administrators to specify OpenSSL options to be used on connections;
933 typically this is to set bug compatibility features which the OpenSSL
934 developers have not enabled by default. There may be security
935 consequences for certain options, so these should not be changed
938 2. A new pipe transport option, "permit_coredumps", may help with problem
939 diagnosis in some scenarios. Note that Exim is typically installed as
940 a setuid binary, which on most OSes will inhibit coredumps by default,
941 so that safety mechanism would have to be overridden for this option to
942 be able to take effect.
944 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
945 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
946 Note that this switches Exim to use a new API ("INSTREAM") and a future
947 release of ClamAV will remove support for the old API ("STREAM").
949 The av_scanner option, when set to "clamd", now takes an optional third
950 part, "local", which causes Exim to pass a filename to ClamAV instead of
951 the file content. This is the same behaviour as when clamd is pointed at
952 a Unix-domain socket. For example:
954 av_scanner = clamd:192.0.2.3 1234:local
956 ClamAV's ExtendedDetectionInfo response format is now handled.
958 4. There is now a -bmalware option, restricted to admin users. This option
959 takes one parameter, a filename, and scans that file with Exim's
960 malware-scanning framework. This is intended purely as a debugging aid
961 to ensure that Exim's scanning is working, not to replace other tools.
962 Note that the ACL framework is not invoked, so if av_scanner references
963 ACL variables without a fallback then this will fail.
965 5. There is a new expansion operator, "reverse_ip", which will reverse IP
966 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
968 ${reverse_ip:192.0.2.4}
970 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
971 -> 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
973 6. There is a new ACL control called "debug", to enable debug logging.
974 This allows selective logging of certain incoming transactions within
975 production environments, with some care. It takes two options, "tag"
976 and "opts"; "tag" is included in the filename of the log and "opts"
977 is used as per the -d<options> command-line option. Examples, which
978 don't all make sense in all contexts:
981 control = debug/tag=.$sender_host_address
982 control = debug/opts=+expand+acl
983 control = debug/tag=.$message_exim_id/opts=+expand
985 7. It has always been implicit in the design and the documentation that
986 "the Exim user" is not root. src/EDITME said that using root was
987 "very strongly discouraged". This is not enough to keep people from
988 shooting themselves in the foot in days when many don't configure Exim
989 themselves but via package build managers. The security consequences of
990 running various bits of network code are severe if there should be bugs in
991 them. As such, the Exim user may no longer be root. If configured
992 statically, Exim will refuse to build. If configured as ref:user then Exim
993 will exit shortly after start-up. If you must shoot yourself in the foot,
994 then henceforth you will have to maintain your own local patches to strip
997 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
998 condition logic to determine truth/failure and will fail to expand many
999 strings, bool_lax{} uses the router condition logic, where most strings
1001 Note: bool{00} is false, bool_lax{00} is true.
1003 9. Routers now support multiple "condition" tests.
1005 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
1006 Setting this allows an admin to define which entry in the tcpwrappers
1007 config file will be used to control access to the daemon. This option
1008 is only available when Exim is built with USE_TCP_WRAPPERS. The
1009 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
1012 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
1013 the Exim run-time user, instead of root.
1015 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
1016 is forced on. This is mitigated by the new build option
1017 TRUSTED_CONFIG_LIST which defines a list of configuration files which
1018 are trusted; one per line. If a config file is owned by root and matches
1019 a pathname in the list, then it may be invoked by the Exim build-time
1020 user without Exim relinquishing root privileges.
1022 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
1023 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
1024 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
1025 include the main config. As a transition mechanism, we are temporarily
1026 providing a work-around: the new build option WHITELIST_D_MACROS provides
1027 a colon-separated list of macro names which may be overridden by the Exim
1028 run-time user. The values of these macros are constrained to the regex
1029 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
1035 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
1036 writable, the other to locking of MBX folders (not mbox).
1038 2. MySQL stored procedures are now supported.
1040 3. The dkim_domain transport option is now a list, not a single string, and
1041 messages will be signed for each element in the list (discarding
1044 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
1045 in the presence of multiple character strings within the RR. Prior to 4.70,
1046 only the first string would be returned. The dnsdb lookup now, by default,
1047 preserves the pre-4.70 semantics, but also now takes an extended output
1048 separator specification. The separator can be followed by a semicolon, to
1049 concatenate the individual text strings together with no join character,
1050 or by a comma and a second separator character, in which case the text
1051 strings within a TXT record are joined on that second character.
1052 Administrators are reminded that DNS provides no ordering guarantees
1053 between multiple records in an RRset. For example:
1055 foo.example. IN TXT "a" "b" "c"
1056 foo.example. IN TXT "d" "e" "f"
1058 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
1059 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
1060 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
1066 1. Native DKIM support without an external library.
1067 (Note that if no action to prevent it is taken, a straight upgrade will
1068 result in DKIM verification of all signed incoming emails. See spec
1069 for details on conditionally disabling)
1071 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
1073 3. There is now a bool{} expansion condition which maps certain strings to
1074 true/false condition values (most likely of use in conjunction with the
1075 and{} expansion operator).
1077 4. The $spam_score, $spam_bar and $spam_report variables are now available
1080 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
1081 options, provided that Exim is invoked by an admin_user.
1083 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
1084 which increases compatibility with older clients at the cost of decreased
1085 security. Don't set this unless you need to support such clients.
1087 7. There is a new expansion operator, ${randint:...} which will produce a
1088 "random" number less than the supplied integer. This randomness is
1089 not guaranteed to be cryptographically strong, but depending upon how
1090 Exim was built may be better than the most naive schemes.
1092 8. Exim now explicitly ensures that SHA256 is available when linked against
1095 9. The transport_filter_timeout option now applies to SMTP transports too.
1101 1. Preliminary DKIM support in Experimental.
1107 1. The body_linecount and body_zerocount C variables are now exported in the
1110 2. When a dnslists lookup succeeds, the key that was looked up is now placed
1111 in $dnslist_matched. When the key is an IP address, it is not reversed in
1112 this variable (though it is, of course, in the actual lookup). In simple
1115 deny dnslists = spamhaus.example
1117 the key is also available in another variable (in this case,
1118 $sender_host_address). In more complicated cases, however, this is not
1119 true. For example, using a data lookup might generate a dnslists lookup
1122 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
1124 If this condition succeeds, the value in $dnslist_matched might be
1125 192.168.6.7 (for example).
1127 3. Authenticators now have a client_condition option. When Exim is running as
1128 a client, it skips an authenticator whose client_condition expansion yields
1129 "0", "no", or "false". This can be used, for example, to skip plain text
1130 authenticators when the connection is not encrypted by a setting such as:
1132 client_condition = ${if !eq{$tls_cipher}{}}
1134 Note that the 4.67 documentation states that $tls_cipher contains the
1135 cipher used for incoming messages. In fact, during SMTP delivery, it
1136 contains the cipher used for the delivery. The same is true for
1139 4. There is now a -Mvc <message-id> option, which outputs a copy of the
1140 message to the standard output, in RFC 2822 format. The option can be used
1141 only by an admin user.
1143 5. There is now a /noupdate option for the ratelimit ACL condition. It
1144 computes the rate and checks the limit as normal, but it does not update
1145 the saved data. This means that, in relevant ACLs, it is possible to lookup
1146 the existence of a specified (or auto-generated) ratelimit key without
1147 incrementing the ratelimit counter for that key.
1149 In order for this to be useful, another ACL entry must set the rate
1150 for the same key somewhere (otherwise it will always be zero).
1155 # Read the rate; if it doesn't exist or is below the maximum
1156 # we update it below
1157 deny ratelimit = 100 / 5m / strict / noupdate
1158 log_message = RATE: $sender_rate / $sender_rate_period \
1159 (max $sender_rate_limit)
1161 [... some other logic and tests...]
1163 warn ratelimit = 100 / 5m / strict / per_cmd
1164 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
1165 (max $sender_rate_limit)
1166 condition = ${if le{$sender_rate}{$sender_rate_limit}}
1170 6. The variable $max_received_linelength contains the number of bytes in the
1171 longest line that was received as part of the message, not counting the
1172 line termination character(s).
1174 7. Host lists can now include +ignore_defer and +include_defer, analogous to
1175 +ignore_unknown and +include_unknown. These options should be used with
1176 care, probably only in non-critical host lists such as whitelists.
1178 8. There's a new option called queue_only_load_latch, which defaults true.
1179 If set false when queue_only_load is greater than zero, Exim re-evaluates
1180 the load for each incoming message in an SMTP session. Otherwise, once one
1181 message is queued, the remainder are also.
1183 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
1184 cases when an SMTP session ends without sending QUIT. However, when Exim
1185 itself is is bad trouble, such as being unable to write to its log files,
1186 this ACL is not run, because it might try to do things (such as write to
1187 log files) that make the situation even worse.
1189 Like the QUIT ACL, this new ACL is provided to make it possible to gather
1190 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
1191 modifier is forbidden in this ACL.
1193 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
1194 to a string that indicates the reason for the termination of the SMTP
1195 connection. The possible values are:
1197 acl-drop Another ACL issued a "drop" command
1198 bad-commands Too many unknown or non-mail commands
1199 command-timeout Timeout while reading SMTP commands
1200 connection-lost The SMTP connection has been lost
1201 data-timeout Timeout while reading message data
1202 local-scan-error The local_scan() function crashed
1203 local-scan-timeout The local_scan() function timed out
1204 signal-exit SIGTERM or SIGINT
1205 synchronization-error SMTP synchronization error
1206 tls-failed TLS failed to start
1208 In most cases when an SMTP connection is closed without having received
1209 QUIT, Exim sends an SMTP response message before actually closing the
1210 connection. With the exception of acl-drop, the default message can be
1211 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
1212 "drop" verb in another ACL, it is the message from the other ACL that is
1215 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
1216 servers with individual queries. This is done by starting the query with
1217 "servers=x:y:z;", where each item in the list may take one of two forms:
1219 (1) If it is just a host name, the appropriate global option (mysql_servers
1220 or pgsql_servers) is searched for a host of the same name, and the
1221 remaining parameters (database, user, password) are taken from there.
1223 (2) If it contains any slashes, it is taken as a complete parameter set.
1225 The list of servers is used in exactly the same was as the global list.
1226 Once a connection to a server has happened and a query has been
1227 successfully executed, processing of the lookup ceases.
1229 This feature is intended for use in master/slave situations where updates
1230 are occurring, and one wants to update a master rather than a slave. If the
1231 masters are in the list for reading, you might have:
1233 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1235 In an updating lookup, you could then write
1237 ${lookup mysql{servers=master; UPDATE ...}
1239 If, on the other hand, the master is not to be used for reading lookups:
1241 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1243 you can still update the master by
1245 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1247 11. The message_body_newlines option (default FALSE, for backwards
1248 compatibility) can be used to control whether newlines are present in
1249 $message_body and $message_body_end. If it is FALSE, they are replaced by
1256 1. There is a new log selector called smtp_no_mail, which is not included in
1257 the default setting. When it is set, a line is written to the main log
1258 whenever an accepted SMTP connection terminates without having issued a
1261 2. When an item in a dnslists list is followed by = and & and a list of IP
1262 addresses, the behaviour was not clear when the lookup returned more than
1263 one IP address. This has been solved by the addition of == and =& for "all"
1264 rather than the default "any" matching.
1266 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1267 for the cipher algorithms. New options have been added to allow some of the
1268 other parameters to be varied.
1270 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1271 set, Exim compiles a runtime option called disable_fsync.
1273 5. There is a new variable called $smtp_count_at_connection_start.
1275 6. There's a new control called no_pipelining.
1277 7. There are two new variables called $sending_ip_address and $sending_port.
1278 These are set whenever an SMTP connection to another host has been set up.
1280 8. The expansion of the helo_data option in the smtp transport now happens
1281 after the connection to the server has been made.
1283 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1284 are encoded as per RFC 2047.
1286 10. There is a new log selector called "pid", which causes the current process
1287 id to be added to every log line, in square brackets, immediately after the
1290 11. Exim has been modified so that it flushes SMTP output before implementing
1291 a delay in an ACL. It also flushes the output before performing a callout,
1292 as this can take a substantial time. These behaviours can be disabled by
1293 obeying control = no_delay_flush or control = no_callout_flush,
1294 respectively, at some earlier stage of the connection.
1296 12. There are two new expansion conditions that iterate over a list. They are
1297 called forany and forall.
1299 13. There's a new global option called dsn_from that can be used to vary the
1300 contents of From: lines in bounces and other automatically generated
1301 messages ("delivery status notifications" - hence the name of the option).
1303 14. The smtp transport has a new option called hosts_avoid_pipelining.
1305 15. By default, exigrep does case-insensitive matches. There is now a -I option
1306 that makes it case-sensitive.
1308 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1309 been added to string expansions to make it easier to process lists of
1310 items, typically addresses.
1312 17. There's a new ACL modifier called "continue". It does nothing of itself,
1313 and processing of the ACL always continues with the next condition or
1314 modifier. It is provided so that the side effects of expanding its argument
1317 18. It is now possible to use newline and other control characters (those with
1318 values less than 32, plus DEL) as separators in lists.
1320 19. The exigrep utility now has a -v option, which inverts the matching
1323 20. The host_find_failed option in the manualroute router can now be set to
1330 No new features were added to 4.66.
1336 No new features were added to 4.65.
1342 1. ACL variables can now be given arbitrary names, as long as they start with
1343 "acl_c" or "acl_m" (for connection variables and message variables), are at
1344 least six characters long, with the sixth character being either a digit or
1347 2. There is a new ACL modifier called log_reject_target. It makes it possible
1348 to specify which logs are used for messages about ACL rejections.
1350 3. There is a new authenticator called "dovecot". This is an interface to the
1351 authentication facility of the Dovecot POP/IMAP server, which can support a
1352 number of authentication methods.
1354 4. The variable $message_headers_raw provides a concatenation of all the
1355 messages's headers without any decoding. This is in contrast to
1356 $message_headers, which does RFC2047 decoding on the header contents.
1358 5. In a DNS black list, if two domain names, comma-separated, are given, the
1359 second is used first to do an initial check, making use of any IP value
1360 restrictions that are set. If there is a match, the first domain is used,
1361 without any IP value restrictions, to get the TXT record.
1363 6. All authenticators now have a server_condition option.
1365 7. There is a new command-line option called -Mset. It is useful only in
1366 conjunction with -be (that is, when testing string expansions). It must be
1367 followed by a message id; Exim loads the given message from its spool
1368 before doing the expansions.
1370 8. Another similar new command-line option is called -bem. It operates like
1371 -be except that it must be followed by the name of a file that contains a
1374 9. When an address is delayed because of a 4xx response to a RCPT command, it
1375 is now the combination of sender and recipient that is delayed in
1376 subsequent queue runs until its retry time is reached.
1378 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1379 shift, have been added to the eval: and eval10: expansion items.
1381 11. The variables $interface_address and $interface_port have been renamed
1382 as $received_ip_address and $received_port, to make it clear that they
1383 relate to message reception rather than delivery. (The old names remain
1384 available for compatibility.)
1386 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1387 to vary the message that is sent when an SMTP command is accepted.
1393 1. There is a new Boolean option called filter_prepend_home for the redirect
1396 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1397 start of receiving a non-SMTP message, before any of the message has been
1400 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1401 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1402 start of the message for an SMTP error code.
1404 4. There is a new parameter for LDAP lookups called "referrals", which takes
1405 one of the settings "follow" (the default) or "nofollow".
1407 5. Version 20070721.2 of exipick now included, offering these new options:
1409 After all other sorting options have bee processed, reverse order
1410 before displaying messages (-R is synonym).
1412 Randomize order of matching messages before displaying.
1414 Instead of displaying the matching messages, display the sum
1416 --sort <variable>[,<variable>...]
1417 Before displaying matching messages, sort the messages according to
1418 each messages value for each variable.
1420 Negate the value for every test (returns inverse output from the
1421 same criteria without --not).
1427 1. The ${readsocket expansion item now supports Internet domain sockets as well
1428 as Unix domain sockets. If the first argument begins "inet:", it must be of
1429 the form "inet:host:port". The port is mandatory; it may be a number or the
1430 name of a TCP port in /etc/services. The host may be a name, or it may be an
1431 IP address. An ip address may optionally be enclosed in square brackets.
1432 This is best for IPv6 addresses. For example:
1434 ${readsocket{inet:[::1]:1234}{<request data>}...
1436 Only a single host name may be given, but if looking it up yield more than
1437 one IP address, they are each tried in turn until a connection is made. Once
1438 a connection has been made, the behaviour is as for ${readsocket with a Unix
1441 2. If a redirect router sets up file or pipe deliveries for more than one
1442 incoming address, and the relevant transport has batch_max set greater than
1443 one, a batch delivery now occurs.
1445 3. The appendfile transport has a new option called maildirfolder_create_regex.
1446 Its value is a regular expression. For a maildir delivery, this is matched
1447 against the maildir directory; if it matches, Exim ensures that a
1448 maildirfolder file is created alongside the new, cur, and tmp directories.
1454 The documentation is up-to-date for the 4.61 release. Major new features since
1455 the 4.60 release are:
1457 . An option called disable_ipv6, to disable the use of IPv6 completely.
1459 . An increase in the number of ACL variables to 20 of each type.
1461 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1462 $2, $3, (though those are still set) because the numeric variables get used
1463 for other things in complicated expansions.
1465 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1467 . It is possible to use setclassresources() on some BSD OS to control the
1468 resources used in pipe deliveries.
1470 . A new ACL modifier called add_header, which can be used with any verb.
1472 . More errors are detectable in retry rules.
1474 There are a number of other additions too.
1480 The documentation is up-to-date for the 4.60 release. Major new features since
1481 the 4.50 release are:
1483 . Support for SQLite.
1485 . Support for IGNOREQUOTA in LMTP.
1487 . Extensions to the "submission mode" features.
1489 . Support for Client SMTP Authorization (CSA).
1491 . Support for ratelimiting hosts and users.
1493 . New expansion items to help with the BATV "prvs" scheme.
1495 . A "match_ip" condition, that matches an IP address against a list.
1497 There are many more minor changes.