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 fast-ramp two phase queue run support, previously experimental, is
13 now supported by default.
15 2. The native SRS support, previously experimental, is now supported. It is
16 not built unless specified in the Local/Makefile.
18 3. TLS resumption support, previously experimental, is now supported and
19 included in default builds.
21 4. Single-key LMDB lookups, previously experimental, are now supported.
22 The support is not built unless specified in the Local/Makefile.
24 5. Option "message_linelength_limit" on the smtp transport to enforce (by
25 default) the RFC 998 character limit.
27 6. An option to ignore the cache on a lookup.
29 7. Quota checking during reception (i.e. at SMTP time) for appendfile-
30 transport-managed quotas.
32 8. Sqlite lookups accept a "file=<path>" option to specify a per-operation
33 db file, replacing the previous prefix to the SQL string (which had
34 issues when the SQL used tainted values).
36 9. Lsearch lookups accept a "ret=full" option, to return both the portion
37 of the line matching the key, and the remainder.
39 10. A command-line option to have a daemon not create a notifier socket.
41 11. Faster TLS startup. When various configuration options contain no
42 expandable elements, the information can be preloaded and cached rather
43 than the provious behaviour of always loading at startup time for every
44 connection. This helps particularly for the CA bundle.
46 12. Proxy Protocol Timeout is configurable via "proxy_protocol_timeout"
49 13. Option "smtp_accept_msx_per_connection" is now expanded.
54 1. EXPERIMENTAL_SRS_NATIVE optional build feature. See the experimental.spec
57 2. Channel-binding for authenticators is now supported under OpenSSL.
58 Previously it was GnuTLS-only.
62 4. Client-side support in the gsasl authenticator. Tested against the
63 plaintext driver for PLAIN; only against itself for SCRAM-SHA-1 and
64 SCRAM-SHA-1-PLUS methods.
66 5. Server-side support in the gsasl authenticator for encrypted passwords, as
67 an alternate for the existing plaintext.
69 6. Variable $local_part_data now also set by router check_local_user option,
70 with an de-tainted version of $local_part.
72 7. Named-list definitions can now be prefixed "hide" so that "-bP" commands do
73 not output the content. Previously this could only be done on options.
75 8. As an experimental feature, the dovecot authentication driver supports inet
76 sockets. Previously it was unix-domain sockets only.
78 9. The ACL control "queue_only" can also be spelled "queue", and now takes an
79 option "first_pass_route" to do the same as a "-odqs" on the command line.
81 10. Items specified for the router and transport headers_remove option can use
82 a trailing asterisk to specify globbing.
84 11. New $queue_size variable.
86 12. New variables $local_part_{pre,suf}fix_v.
88 13. New main option "sqlite_dbfile", for use in preference to prefixing the
89 lookup string. The older method fails when tainted variables are used
90 in the lookup, as the filename becomes tainted. The new method keeps the
93 14. Options on the dsearch lookup, to return the full path and to filter
94 filetypes for matching.
96 15. Options on pgsql and mysql lookups, to specify server separate from the
99 16. An option on all single-key lookups, to return (on a hit) a de-tainted
100 version of the lookup key rather than the looked-up data.
102 17. $domain_data and $local_part_data are now set by all list-match successes.
103 Previously only list items that performed lookups did so.
104 Also, matching list items that are tail-match or RE-match now set the
105 numeric variables $0 (etc) in the same way os other RE matches.
107 18. Expansion item ${listquote {<char} {<item>}}.
109 19. An option for the ${readsocket {}{}{}} expansion to make the result data
112 20. dkim_verify_min_keysizes, a list of minimum acceptable public-key sizes.
114 21. bounce_message_file and warn_message_file are now expanded before use.
116 22. New main config option spf_smtp_comment_template to customise the
117 $spf_smtp_comment variable
124 1. An "external" authenticator, per RFC 4422 Appendix A.
126 2. A JSON lookup type, and JSON variants of the forall/any expansion conditions.
128 3. Variables $tls_in_cipher_std, $tls_out_cipher_std giving the RFC names
131 4. Log_selectors "msg_id" (on by default) and "msg_id_created".
133 5. A case_insensitive option for verify=not_blind.
135 6. EXPERIMENTAL_TLS_RESUME optional build feature. See the experimental.spec
138 7. A main option exim_version to override the version Exim
139 reports in verious places ($exim_version, $version_number).
141 8. Expansion operator ${sha2_N:} for N=256, 384, 512.
143 9. Router variables, $r_... settable from router options and usable in routers
146 10. The spf lookup now supports IPv6.
148 11. Main options for DKIM verify to filter hash and key types.
150 12. With TLS1.3, support for full-chain OCSP stapling.
152 13. Dual-certificate stacks on servers now support OCSP stapling, under OpenSSL.
154 14: An smtp:ehlo transport event, for observability of the remote offered features.
156 15: Support under OpenSSL for writing NSS-style key files for packet-capture
157 decode. The environment variable SSLKEYLOGFILE is used; if an absolute path
158 it must indicate a file under the spool directory; if relative the the spool
159 directory is prepended. Works on the server side only. Support under
160 GnuTLS was already there, being done purely by the library (server side
161 only, and exim must be run as root).
163 16: Command-line option to move messages from one named queue to another.
165 17. Variables $tls_in_ver, $tls_out_ver.
171 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
172 list when there are multiple headers having a given name. This matters
173 when individual headers are wrapped onto multiple lines; with previous
174 facilities hard to parse.
176 2. The ${readsocket } expansion item now takes a "tls" option, doing the
179 3. EXPERIMENTAL_REQUIRETLS and EXPERIMENTAL_PIPE_CONNECT optional build
180 features. See the experimental.spec file.
182 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
184 5. A "pipelining" log_selector.
186 6. Builtin macros for supported log_selector and openssl_options values.
188 7. JSON variants of the ${extract } expansion item.
190 8. A "noutf8" debug option, for disabling the UTF-8 characters in debug output.
192 9. TCP Fast Open support on MacOS.
197 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
198 version 3.5.6 or later.
200 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
201 OpenSSL versions are moved to mainline support from Experimental.
202 New SMTP transport option "dane_require_tls_ciphers".
204 3. Feature macros for the compiled-in set of malware scanner interfaces.
206 4. SPF support is promoted from Experimental to mainline status. The template
207 src/EDITME makefile does not enable its inclusion.
209 5. Logging control for DKIM verification. The existing DKIM log line is
210 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
211 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
212 a "dkim" log_selector.
214 6. Receive duration on <= lines, under a new log_selector "receive_time".
216 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
217 routing rules in the manualroute router.
219 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
220 under OpenSSL version 1.1.1 or later.
222 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
223 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
225 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
228 11. "exim -bP macro <name>" returns caller-usable status.
230 12. Expansion item ${authresults {<machine>}} for creating an
231 Authentication-Results: header.
233 13. EXPERIMENTAL_ARC. See the experimental.spec file.
234 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
236 14: A dane:fail event, intended to facilitate reporting.
238 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
239 contain all the servers in the cluster, all of which must be reachable from
240 the running exim instance. If the cluster has master/slave replication, the
241 list must contain all the master and slave servers.
243 16. Add an option to the Avast scanner interface: "pass_unscanned". This
244 allows to treat unscanned files as clean. Files may be unscanned for
245 several reasons: decompression bombs, broken archives.
251 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
252 wildcards will be expanded, values are collapsed.
254 2. The ${readsocket } expansion now takes an option to not shutdown the
255 connection after sending the query string. The default remains to do so.
257 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
258 deliveries on a single TCP connection can maintain a TLS connection
259 open. By default disabled for all hosts, doing so saves the cost of
260 making new TLS sessions, at the cost of having to proxy the data via
261 another process. Logging is also affected.
263 4. A malware connection type for the FPSCAND protocol.
265 5. An option for recipient verify callouts to hold the connection open for
266 further recipients and for delivery.
268 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
271 7. Optionally, an alternate format for spool data-files which matches the
272 wire format - meaning more efficient reception and transmission (at the
273 cost of difficulty with standard Unix tools). Only used for messages
274 received using the ESMTP CHUNKING option, and when a new main-section
275 option "spool_wireformat" (false by default) is set.
277 8. New main configuration option "commandline_checks_require_admin" to
278 restrict who can use various introspection options.
280 9. New option modifier "no_check" for quota and quota_filecount
281 appendfile transport.
283 10. Variable $smtp_command_history returning a comma-sep list of recent
286 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
287 log elements QT, DT and D, and timstamps in debug output.
289 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
290 while still in SYN_RECV state; as a client logs when the connection
291 is opened with a TFO cookie.
293 13. DKIM support for multiple signing, by domain and/or key-selector.
294 DKIM support for multiple hashes, and for alternate-identity tags.
295 Builtin macro with default list of signed headers.
296 Better syntax for specifying oversigning.
297 The DKIM ACL can override verification status, and status is visible in
300 14. Exipick understands -C|--config for an alternative Exim
303 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
304 for ${readsocket } expansions, and for ClamAV.
306 16. The "-be" expansion test mode now supports macros. Macros are expanded
307 in test lines, and new macros can be defined.
309 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
315 1. Allow relative config file names for ".include"
317 2. A main-section config option "debug_store" to control the checks on
318 variable locations during store-reset. Normally false but can be enabled
319 when a memory corruption issue is suspected on a production system.
325 1. The new perl_taintmode option allows to run the embedded perl
326 interpreter in taint mode.
328 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
330 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
333 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
334 N can be 224, 256 (default), 384, 512.
335 With GnuTLS 3.5.0 or later, only.
337 5. Facility for named queues: A command-line argument can specify
338 the queue name for a queue operation, and an ACL modifier can set
339 the queue to be used for a message. A $queue_name variable gives
342 6. New expansion operators base32/base32d.
344 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
345 performance increase and network load decrease. Main config option
346 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
349 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
351 9. Expansion operator escape8bit, like escape but not touching newline etc..
353 10. Feature macros, generated from compile options. All start with "_HAVE_"
354 and go on with some roughly recognisable name. Driver macros, for
355 router, transport and authentication drivers; names starting with "_DRIVER_".
356 Option macros, for each configuration-file option; all start with "_OPT_".
357 Use the "-bP macros" command-line option to see what is present.
359 11. Integer values for options can take a "G" multiplier.
361 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
362 returns from the target back to the initiator, rather than spooling the
365 13. New built-in constants available for tls_dhparam and default changed.
367 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
368 out copies of the message spool files for use by 3rd-party scanners.
370 15. A new option on the smtp transport, hosts_try_fastopen. If the system
371 supports it (on Linux it must be enabled in the kernel by the sysadmin)
372 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
373 but it permits a peer that also supports the facility to send its SMTP
374 banner immediately after the SYN,ACK segment rather then waiting for
375 another ACK - so saving up to one roundtrip time. Because it requires
376 previous communication with the peer (we save a cookie from it) this
377 will only become active on frequently-contacted destinations.
379 16. A new syslog_pid option to suppress PID duplication in syslog lines.
385 1. The ACL conditions regex and mime_regex now capture substrings
386 into numeric variables $regex1 to 9, like the "match" expansion condition.
388 2. New $callout_address variable records the address used for a spam=,
389 malware= or verify= callout.
391 3. Transports now take a "max_parallel" option, to limit concurrency.
393 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
394 The latter expands to a 8-element colon-sep set of hex digits including
395 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
396 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
397 The former operator strips leading zeroes and collapses the longest
398 set of 0-groups to a double-colon.
400 5. New "-bP config" support, to dump the effective configuration.
402 6. New $dkim_key_length variable.
404 7. New base64d and base64 expansion items (the existing str2b64 being a
405 synonym of the latter). Add support in base64 for certificates.
407 8. New main configuration option "bounce_return_linesize_limit" to
408 avoid oversize bodies in bounces. The default value matches RFC
411 9. New $initial_cwd expansion variable.
417 1. Support for using the system standard CA bundle.
419 2. New expansion items $config_file, $config_dir, containing the file
420 and directory name of the main configuration file. Also $exim_version.
422 3. New "malware=" support for Avast.
424 4. New "spam=" variant option for Rspamd.
426 5. Assorted options on malware= and spam= scanners.
428 6. A command-line option to write a comment into the logfile.
430 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
431 be configured to make connections via socks5 proxies.
433 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
434 the transmission of UTF-8 envelope addresses.
436 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
437 used encoding of Maildir folder names.
439 10. A logging option for slow DNS lookups.
441 11. New ${env {<variable>}} expansion.
443 12. A non-SMTP authenticator using information from TLS client certificates.
445 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
446 Patch originally by Wolfgang Breyha.
448 14. Main option "dns_trust_aa" for trusting your local nameserver at the
449 same level as DNSSEC.
454 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
455 DANE SMTP draft to assess a secure chain of trust of the certificate
456 used to establish the TLS connection based on a TLSA record in the
457 domain of the sender.
459 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
460 and several new events have been created. The reason is because it has
461 been expanded beyond just firing events during the transport phase. Any
462 existing TPDA transport options will have to be rewritten to use a new
463 $event_name expansion variable in a condition. Refer to the
464 experimental-spec.txt for details and examples.
466 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
467 server certs used for TLS match the result of the MX lookup. It does
468 not use the same mechanism as DANE.
478 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
479 configured to expect an initial header from a proxy that will make the
480 actual external source IP:host be used in exim instead of the IP of the
481 proxy that is connecting to it.
483 2. New verify option header_names_ascii, which will check to make sure
484 there are no non-ASCII characters in header names. Exim itself handles
485 those non-ASCII characters, but downstream apps may not, so Exim can
486 detect and reject if those characters are present.
488 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
489 codepoints with valid ones.
491 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
492 command line and matching a regex against the return data for trigger
493 and a second regex to extract malware_name. The mail spoolfile name can
494 be included in the command line.
496 5. The smtp transport now supports options "tls_verify_hosts" and
497 "tls_try_verify_hosts". If either is set the certificate verification
498 is split from the encryption operation. The default remains that a failed
499 verification cancels the encryption.
501 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
502 lookup can now set a list of servers to use that is different from the
505 7. New command-line option -C for exiqgrep to specify alternate exim.conf
506 file when searching the queue.
508 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
510 9. Support for DNSSEC on outbound connections.
512 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
513 "certextract" to extract fields from them. Hash operators md5 and sha1
514 work over them for generating fingerprints, and a new sha256 operator
517 11. PRDR is now supported dy default.
519 12. OCSP stapling is now supported by default.
521 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
522 Delivery Status Notification messages in MIME format, and negotiate
523 DSN features per RFC 3461.
529 1. New command-line option -bI:sieve will list all supported sieve extensions
530 of this Exim build on standard output, one per line.
531 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
532 query this to establish the correct list to include in the protocol's
533 SIEVE capability line.
535 2. If the -n option is combined with the -bP option, then the name of an
536 emitted option is not output, only the value (if visible to you).
537 For instance, "exim -n -bP pid_file_path" should just emit a pathname
538 followed by a newline, and no other text.
540 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
541 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
542 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
543 acceptable for security. (Option accepted but ignored if using OpenSSL).
544 Defaults to 1024, the old value. May be lowered only to 512, or raised as
545 far as you like. Raising this may hinder TLS interoperability with other
546 sites and is not currently recommended. Lowering this will permit you to
547 establish a TLS session which is not as secure as you might like.
549 Unless you really know what you are doing, leave it alone.
551 4. If not built with DISABLE_DNSSEC, Exim now has the main option
552 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
553 to send the DO flag to your recursive resolver. If you have a recursive
554 resolver, which can set the Authenticated Data (AD) flag in results, Exim
555 can now detect this. Exim does not perform validation itself, instead
556 relying upon a trusted path to the resolver.
558 Current status: work-in-progress; $sender_host_dnssec variable added.
560 5. DSCP support for outbound connections: on a transport using the smtp driver,
561 set "dscp = ef", for instance, to cause the connections to have the relevant
562 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
564 Similarly for inbound connections, there is a new control modifier, dscp,
565 so "warn control = dscp/ef" in the connect ACL, or after authentication.
567 Supported values depend upon system libraries. "exim -bI:dscp" to list the
568 ones Exim knows of. You can also set a raw number 0..0x3F.
570 6. The -G command-line flag is no longer ignored; it is now equivalent to an
571 ACL setting "control = suppress_local_fixups". The -L command-line flag
572 is now accepted and forces use of syslog, with the provided tag as the
573 process name. A few other flags used by Sendmail are now accepted and
576 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
577 ACL modifier; works for single-recipient mails which are received on and
578 deliverable via SMTP. Using the connection made for a recipient verify,
579 if requested before the verify, or a new one made for the purpose while
580 the inbound connection is still active. The bulk of the mail item is copied
581 direct from the inbound socket to the outbound (as well as the spool file).
582 When the source notifies the end of data, the data acceptance by the destination
583 is negotiated before the acceptance is sent to the source. If the destination
584 does not accept the mail item, for example due to content-scanning, the item
585 is not accepted from the source and therefore there is no need to generate
586 a bounce mail. This is of benefit when providing a secondary-MX service.
587 The downside is that delays are under the control of the ultimate destination
590 The Received-by: header on items delivered by cutthrough is generated
591 early in reception rather than at the end; this will affect any timestamp
592 included. The log line showing delivery is recorded before that showing
593 reception; it uses a new ">>" tag instead of "=>".
595 To support the feature, verify-callout connections can now use ESMTP and TLS.
596 The usual smtp transport options are honoured, plus a (new, default everything)
597 hosts_verify_avoid_tls.
599 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
600 for specific access to the information for each connection. The old names
601 are present for now but deprecated.
603 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
605 8. New expansion operators ${listnamed:name} to get the content of a named list
606 and ${listcount:string} to count the items in a list.
608 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
609 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
610 modules. For some situations this is desirable, but we expect admin in
611 those situations to know they want the feature. More commonly, it means
612 that GUI user modules get loaded and are broken by the setuid Exim being
613 unable to access files specified in environment variables and passed
614 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
615 unless this new option is set.
617 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
618 so have also added a build option which can be used to build Exim with GnuTLS
619 but without trying to use any kind of PKCS11 support. Uncomment this in the
622 AVOID_GNUTLS_PKCS11=yes
624 10. The "acl = name" condition on an ACL now supports optional arguments.
625 New expansion item "${acl {name}{arg}...}" and expansion condition
626 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
627 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
628 Variable $acl_narg contains the number of arguments. If the ACL sets
629 a "message =" value this becomes the result of the expansion item,
630 or the value of $value for the expansion condition. If the ACL returns
631 accept the expansion condition is true; if reject, false. A defer
632 return results in a forced fail.
634 11. Routers and transports can now have multiple headers_add and headers_remove
635 option lines. The concatenated list is used.
637 12. New ACL modifier "remove_header" can remove headers before message gets
638 handled by routers/transports.
640 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
641 "aaaa" and "a" lookups is done and the full set of results returned.
643 14. New expansion variable $headers_added with content from ACL add_header
644 modifier (but not yet added to message).
646 15. New 8bitmime status logging option for received messages. Log field "M8S".
648 16. New authenticated_sender logging option, adding to log field "A".
650 17. New expansion variables $router_name and $transport_name. Useful
651 particularly for debug_print as -bt command-line option does not
652 require privilege whereas -d does.
654 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
655 proposed extension to SMTP from Eric Hall.
657 19. The pipe transport has gained the force_command option, to allow
658 decorating commands from user .forward pipe aliases with prefix
659 wrappers, for instance.
661 20. Callout connections can now AUTH; the same controls as normal delivery
664 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
665 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
666 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
667 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
668 dmarc_status. It adds new control flags dmarc_disable_verify and
669 dmarc_enable_forensic. The default for the dmarc_tld_file option is
670 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
672 22. Add expansion variable $authenticated_fail_id, which is the username
673 provided to the authentication method which failed. It is available
674 for use in subsequent ACL processing (typically quit or notquit ACLs).
676 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
679 24. New ${hexquote:..string..} expansion operator converts non-printable
680 characters in the string to \xNN form.
682 25. Experimental TPDA (Transport Post Delivery Action) function added.
683 Patch provided by Axel Rau.
685 26. Experimental Redis lookup added. Patch provided by Warren Baker.
691 1. New authenticator driver, "gsasl". Server-only (at present).
692 This is a SASL interface, licensed under GPL, which can be found at
693 http://www.gnu.org/software/gsasl/.
694 This system does not provide sources of data for authentication, so
695 careful use needs to be made of the conditions in Exim.
697 2. New authenticator driver, "heimdal_gssapi". Server-only.
698 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
699 is no longer honoured for setuid programs by Heimdal. Use the
700 "server_keytab" option to point to the keytab.
702 3. The "pkg-config" system can now be used when building Exim to reference
703 cflags and library information for lookups and authenticators, rather
704 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
705 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
706 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
708 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
709 find the headers and libraries for PCRE.
711 4. New expansion variable $tls_bits.
713 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
714 be joined together with ASCII NUL characters to construct the key to pass
715 into the DBM library. Can be used with gsasl to access sasldb2 files as
718 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
720 Avoid release 1.0.1a if you can. Note that the default value of
721 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
722 increased susceptibility to attack. This may still have interoperability
723 implications for very old clients (see version 4.31 change 37) but
724 administrators can choose to make the trade-off themselves and restore
725 compatibility at the cost of session security.
727 7. Use of the new expansion variable $tls_sni in the main configuration option
728 tls_certificate will cause Exim to re-expand the option, if the client
729 sends the TLS Server Name Indication extension, to permit choosing a
730 different certificate; tls_privatekey will also be re-expanded. You must
731 still set these options to expand to valid files when $tls_sni is not set.
733 The SMTP Transport has gained the option tls_sni, which will set a hostname
734 for outbound TLS sessions, and set $tls_sni too.
736 A new log_selector, +tls_sni, has been added, to log received SNI values
737 for Exim as a server.
739 8. The existing "accept_8bitmime" option now defaults to true. This means
740 that Exim is deliberately not strictly RFC compliant. We're following
741 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
742 Those who disagree, or know that they are talking to mail servers that,
743 even today, are not 8-bit clean, need to turn off this option.
745 9. Exim can now be started with -bw (with an optional timeout, given as
746 -bw<timespec>). With this, stdin at startup is a socket that is
747 already listening for connections. This has a more modern name of
748 "socket activation", but forcing the activated socket to fd 0. We're
749 interested in adding more support for modern variants.
751 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
752 for numbers indicates multiplication by 1024^3.
754 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
755 gnutls_require_mac & gnutls_require_protocols are no longer supported.
756 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
757 string, documentation for which is at:
758 http://www.gnutls.org/manual/html_node/Priority-Strings.html
760 SNI support has been added to Exim's GnuTLS integration too.
762 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
763 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
765 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
766 is now available. If the contents of the file are valid, then Exim will
767 send that back in response to a TLS status request; this is OCSP Stapling.
768 Exim will not maintain the contents of the file in any way: administrators
769 are responsible for ensuring that it is up-to-date.
771 See "experimental-spec.txt" for more details.
773 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
774 identically to TXT record lookups.
776 14. New expansion variable $tod_epoch_l for higher-precision time.
778 15. New global option tls_dh_max_bits, defaulting to current value of NSS
779 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
780 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
782 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
783 Option can now be a path or an identifier for a standard prime.
784 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
785 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
788 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
789 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
790 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
796 1. New options for the ratelimit ACL condition: /count= and /unique=.
797 The /noupdate option has been replaced by a /readonly option.
799 2. The SMTP transport's protocol option may now be set to "smtps", to
800 use SSL-on-connect outbound.
802 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
803 there is a problem talking to the AV scanner, or the AV scanner running.
805 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
806 and check if the search item is a member of the list. This does not
807 support named lists, but does subject the list part to string expansion.
809 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
810 built, Exim no longer performs string expansion on the second string of
811 the match_* expansion conditions: "match_address", "match_domain",
812 "match_ip" & "match_local_part". Named lists can still be used.
818 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
819 or off in the resolver library.
825 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
826 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
827 libraries. The following global options have been added in support of
828 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
829 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
831 2. The pipe transport now takes a boolean option, "freeze_signal", default
832 false. When true, if the external delivery command exits on a signal then
833 Exim will freeze the message in the queue, instead of generating a bounce.
835 3. Log filenames may now use %M as an escape, instead of %D (still available).
836 The %M pattern expands to yyyymm, providing month-level resolution.
838 4. The $message_linecount variable is now updated for the maildir_tag option,
839 in the same way as $message_size, to reflect the real number of lines,
840 including any header additions or removals from transport.
842 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
843 Exim now selects entries randomly, to better scale in a cluster setup.
849 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
850 the flaw permitted the Exim run-time user to cause root to append to
851 arbitrary files of the attacker's choosing, with the content based
852 on content supplied by the attacker.
854 2. Exim now supports loading some lookup types at run-time, using your
855 platform's dlopen() functionality. This has limited platform support
856 and the intention is not to support every variant, it's limited to
857 dlopen(). This permits the main Exim binary to not be linked against
858 all the libraries needed for all the lookup types.
864 NOTE: this version is not guaranteed backwards-compatible, please read the
865 items below carefully
867 1. A new main configuration option, "openssl_options", is available if Exim
868 is built with SSL support provided by OpenSSL. The option allows
869 administrators to specify OpenSSL options to be used on connections;
870 typically this is to set bug compatibility features which the OpenSSL
871 developers have not enabled by default. There may be security
872 consequences for certain options, so these should not be changed
875 2. A new pipe transport option, "permit_coredumps", may help with problem
876 diagnosis in some scenarios. Note that Exim is typically installed as
877 a setuid binary, which on most OSes will inhibit coredumps by default,
878 so that safety mechanism would have to be overridden for this option to
879 be able to take effect.
881 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
882 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
883 Note that this switches Exim to use a new API ("INSTREAM") and a future
884 release of ClamAV will remove support for the old API ("STREAM").
886 The av_scanner option, when set to "clamd", now takes an optional third
887 part, "local", which causes Exim to pass a filename to ClamAV instead of
888 the file content. This is the same behaviour as when clamd is pointed at
889 a Unix-domain socket. For example:
891 av_scanner = clamd:192.0.2.3 1234:local
893 ClamAV's ExtendedDetectionInfo response format is now handled.
895 4. There is now a -bmalware option, restricted to admin users. This option
896 takes one parameter, a filename, and scans that file with Exim's
897 malware-scanning framework. This is intended purely as a debugging aid
898 to ensure that Exim's scanning is working, not to replace other tools.
899 Note that the ACL framework is not invoked, so if av_scanner references
900 ACL variables without a fallback then this will fail.
902 5. There is a new expansion operator, "reverse_ip", which will reverse IP
903 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
905 ${reverse_ip:192.0.2.4}
907 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
908 -> 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
910 6. There is a new ACL control called "debug", to enable debug logging.
911 This allows selective logging of certain incoming transactions within
912 production environments, with some care. It takes two options, "tag"
913 and "opts"; "tag" is included in the filename of the log and "opts"
914 is used as per the -d<options> command-line option. Examples, which
915 don't all make sense in all contexts:
918 control = debug/tag=.$sender_host_address
919 control = debug/opts=+expand+acl
920 control = debug/tag=.$message_exim_id/opts=+expand
922 7. It has always been implicit in the design and the documentation that
923 "the Exim user" is not root. src/EDITME said that using root was
924 "very strongly discouraged". This is not enough to keep people from
925 shooting themselves in the foot in days when many don't configure Exim
926 themselves but via package build managers. The security consequences of
927 running various bits of network code are severe if there should be bugs in
928 them. As such, the Exim user may no longer be root. If configured
929 statically, Exim will refuse to build. If configured as ref:user then Exim
930 will exit shortly after start-up. If you must shoot yourself in the foot,
931 then henceforth you will have to maintain your own local patches to strip
934 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
935 condition logic to determine truth/failure and will fail to expand many
936 strings, bool_lax{} uses the router condition logic, where most strings
938 Note: bool{00} is false, bool_lax{00} is true.
940 9. Routers now support multiple "condition" tests.
942 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
943 Setting this allows an admin to define which entry in the tcpwrappers
944 config file will be used to control access to the daemon. This option
945 is only available when Exim is built with USE_TCP_WRAPPERS. The
946 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
949 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
950 the Exim run-time user, instead of root.
952 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
953 is forced on. This is mitigated by the new build option
954 TRUSTED_CONFIG_LIST which defines a list of configuration files which
955 are trusted; one per line. If a config file is owned by root and matches
956 a pathname in the list, then it may be invoked by the Exim build-time
957 user without Exim relinquishing root privileges.
959 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
960 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
961 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
962 include the main config. As a transition mechanism, we are temporarily
963 providing a work-around: the new build option WHITELIST_D_MACROS provides
964 a colon-separated list of macro names which may be overridden by the Exim
965 run-time user. The values of these macros are constrained to the regex
966 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
972 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
973 writable, the other to locking of MBX folders (not mbox).
975 2. MySQL stored procedures are now supported.
977 3. The dkim_domain transport option is now a list, not a single string, and
978 messages will be signed for each element in the list (discarding
981 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
982 in the presence of multiple character strings within the RR. Prior to 4.70,
983 only the first string would be returned. The dnsdb lookup now, by default,
984 preserves the pre-4.70 semantics, but also now takes an extended output
985 separator specification. The separator can be followed by a semicolon, to
986 concatenate the individual text strings together with no join character,
987 or by a comma and a second separator character, in which case the text
988 strings within a TXT record are joined on that second character.
989 Administrators are reminded that DNS provides no ordering guarantees
990 between multiple records in an RRset. For example:
992 foo.example. IN TXT "a" "b" "c"
993 foo.example. IN TXT "d" "e" "f"
995 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
996 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
997 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
1003 1. Native DKIM support without an external library.
1004 (Note that if no action to prevent it is taken, a straight upgrade will
1005 result in DKIM verification of all signed incoming emails. See spec
1006 for details on conditionally disabling)
1008 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
1010 3. There is now a bool{} expansion condition which maps certain strings to
1011 true/false condition values (most likely of use in conjunction with the
1012 and{} expansion operator).
1014 4. The $spam_score, $spam_bar and $spam_report variables are now available
1017 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
1018 options, provided that Exim is invoked by an admin_user.
1020 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
1021 which increases compatibility with older clients at the cost of decreased
1022 security. Don't set this unless you need to support such clients.
1024 7. There is a new expansion operator, ${randint:...} which will produce a
1025 "random" number less than the supplied integer. This randomness is
1026 not guaranteed to be cryptographically strong, but depending upon how
1027 Exim was built may be better than the most naive schemes.
1029 8. Exim now explicitly ensures that SHA256 is available when linked against
1032 9. The transport_filter_timeout option now applies to SMTP transports too.
1038 1. Preliminary DKIM support in Experimental.
1044 1. The body_linecount and body_zerocount C variables are now exported in the
1047 2. When a dnslists lookup succeeds, the key that was looked up is now placed
1048 in $dnslist_matched. When the key is an IP address, it is not reversed in
1049 this variable (though it is, of course, in the actual lookup). In simple
1052 deny dnslists = spamhaus.example
1054 the key is also available in another variable (in this case,
1055 $sender_host_address). In more complicated cases, however, this is not
1056 true. For example, using a data lookup might generate a dnslists lookup
1059 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
1061 If this condition succeeds, the value in $dnslist_matched might be
1062 192.168.6.7 (for example).
1064 3. Authenticators now have a client_condition option. When Exim is running as
1065 a client, it skips an authenticator whose client_condition expansion yields
1066 "0", "no", or "false". This can be used, for example, to skip plain text
1067 authenticators when the connection is not encrypted by a setting such as:
1069 client_condition = ${if !eq{$tls_cipher}{}}
1071 Note that the 4.67 documentation states that $tls_cipher contains the
1072 cipher used for incoming messages. In fact, during SMTP delivery, it
1073 contains the cipher used for the delivery. The same is true for
1076 4. There is now a -Mvc <message-id> option, which outputs a copy of the
1077 message to the standard output, in RFC 2822 format. The option can be used
1078 only by an admin user.
1080 5. There is now a /noupdate option for the ratelimit ACL condition. It
1081 computes the rate and checks the limit as normal, but it does not update
1082 the saved data. This means that, in relevant ACLs, it is possible to lookup
1083 the existence of a specified (or auto-generated) ratelimit key without
1084 incrementing the ratelimit counter for that key.
1086 In order for this to be useful, another ACL entry must set the rate
1087 for the same key somewhere (otherwise it will always be zero).
1092 # Read the rate; if it doesn't exist or is below the maximum
1093 # we update it below
1094 deny ratelimit = 100 / 5m / strict / noupdate
1095 log_message = RATE: $sender_rate / $sender_rate_period \
1096 (max $sender_rate_limit)
1098 [... some other logic and tests...]
1100 warn ratelimit = 100 / 5m / strict / per_cmd
1101 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
1102 (max $sender_rate_limit)
1103 condition = ${if le{$sender_rate}{$sender_rate_limit}}
1107 6. The variable $max_received_linelength contains the number of bytes in the
1108 longest line that was received as part of the message, not counting the
1109 line termination character(s).
1111 7. Host lists can now include +ignore_defer and +include_defer, analogous to
1112 +ignore_unknown and +include_unknown. These options should be used with
1113 care, probably only in non-critical host lists such as whitelists.
1115 8. There's a new option called queue_only_load_latch, which defaults true.
1116 If set false when queue_only_load is greater than zero, Exim re-evaluates
1117 the load for each incoming message in an SMTP session. Otherwise, once one
1118 message is queued, the remainder are also.
1120 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
1121 cases when an SMTP session ends without sending QUIT. However, when Exim
1122 itself is is bad trouble, such as being unable to write to its log files,
1123 this ACL is not run, because it might try to do things (such as write to
1124 log files) that make the situation even worse.
1126 Like the QUIT ACL, this new ACL is provided to make it possible to gather
1127 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
1128 modifier is forbidden in this ACL.
1130 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
1131 to a string that indicates the reason for the termination of the SMTP
1132 connection. The possible values are:
1134 acl-drop Another ACL issued a "drop" command
1135 bad-commands Too many unknown or non-mail commands
1136 command-timeout Timeout while reading SMTP commands
1137 connection-lost The SMTP connection has been lost
1138 data-timeout Timeout while reading message data
1139 local-scan-error The local_scan() function crashed
1140 local-scan-timeout The local_scan() function timed out
1141 signal-exit SIGTERM or SIGINT
1142 synchronization-error SMTP synchronization error
1143 tls-failed TLS failed to start
1145 In most cases when an SMTP connection is closed without having received
1146 QUIT, Exim sends an SMTP response message before actually closing the
1147 connection. With the exception of acl-drop, the default message can be
1148 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
1149 "drop" verb in another ACL, it is the message from the other ACL that is
1152 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
1153 servers with individual queries. This is done by starting the query with
1154 "servers=x:y:z;", where each item in the list may take one of two forms:
1156 (1) If it is just a host name, the appropriate global option (mysql_servers
1157 or pgsql_servers) is searched for a host of the same name, and the
1158 remaining parameters (database, user, password) are taken from there.
1160 (2) If it contains any slashes, it is taken as a complete parameter set.
1162 The list of servers is used in exactly the same was as the global list.
1163 Once a connection to a server has happened and a query has been
1164 successfully executed, processing of the lookup ceases.
1166 This feature is intended for use in master/slave situations where updates
1167 are occurring, and one wants to update a master rather than a slave. If the
1168 masters are in the list for reading, you might have:
1170 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1172 In an updating lookup, you could then write
1174 ${lookup mysql{servers=master; UPDATE ...}
1176 If, on the other hand, the master is not to be used for reading lookups:
1178 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1180 you can still update the master by
1182 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1184 11. The message_body_newlines option (default FALSE, for backwards
1185 compatibility) can be used to control whether newlines are present in
1186 $message_body and $message_body_end. If it is FALSE, they are replaced by
1193 1. There is a new log selector called smtp_no_mail, which is not included in
1194 the default setting. When it is set, a line is written to the main log
1195 whenever an accepted SMTP connection terminates without having issued a
1198 2. When an item in a dnslists list is followed by = and & and a list of IP
1199 addresses, the behaviour was not clear when the lookup returned more than
1200 one IP address. This has been solved by the addition of == and =& for "all"
1201 rather than the default "any" matching.
1203 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1204 for the cipher algorithms. New options have been added to allow some of the
1205 other parameters to be varied.
1207 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1208 set, Exim compiles a runtime option called disable_fsync.
1210 5. There is a new variable called $smtp_count_at_connection_start.
1212 6. There's a new control called no_pipelining.
1214 7. There are two new variables called $sending_ip_address and $sending_port.
1215 These are set whenever an SMTP connection to another host has been set up.
1217 8. The expansion of the helo_data option in the smtp transport now happens
1218 after the connection to the server has been made.
1220 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1221 are encoded as per RFC 2047.
1223 10. There is a new log selector called "pid", which causes the current process
1224 id to be added to every log line, in square brackets, immediately after the
1227 11. Exim has been modified so that it flushes SMTP output before implementing
1228 a delay in an ACL. It also flushes the output before performing a callout,
1229 as this can take a substantial time. These behaviours can be disabled by
1230 obeying control = no_delay_flush or control = no_callout_flush,
1231 respectively, at some earlier stage of the connection.
1233 12. There are two new expansion conditions that iterate over a list. They are
1234 called forany and forall.
1236 13. There's a new global option called dsn_from that can be used to vary the
1237 contents of From: lines in bounces and other automatically generated
1238 messages ("delivery status notifications" - hence the name of the option).
1240 14. The smtp transport has a new option called hosts_avoid_pipelining.
1242 15. By default, exigrep does case-insensitive matches. There is now a -I option
1243 that makes it case-sensitive.
1245 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1246 been added to string expansions to make it easier to process lists of
1247 items, typically addresses.
1249 17. There's a new ACL modifier called "continue". It does nothing of itself,
1250 and processing of the ACL always continues with the next condition or
1251 modifier. It is provided so that the side effects of expanding its argument
1254 18. It is now possible to use newline and other control characters (those with
1255 values less than 32, plus DEL) as separators in lists.
1257 19. The exigrep utility now has a -v option, which inverts the matching
1260 20. The host_find_failed option in the manualroute router can now be set to
1267 No new features were added to 4.66.
1273 No new features were added to 4.65.
1279 1. ACL variables can now be given arbitrary names, as long as they start with
1280 "acl_c" or "acl_m" (for connection variables and message variables), are at
1281 least six characters long, with the sixth character being either a digit or
1284 2. There is a new ACL modifier called log_reject_target. It makes it possible
1285 to specify which logs are used for messages about ACL rejections.
1287 3. There is a new authenticator called "dovecot". This is an interface to the
1288 authentication facility of the Dovecot POP/IMAP server, which can support a
1289 number of authentication methods.
1291 4. The variable $message_headers_raw provides a concatenation of all the
1292 messages's headers without any decoding. This is in contrast to
1293 $message_headers, which does RFC2047 decoding on the header contents.
1295 5. In a DNS black list, if two domain names, comma-separated, are given, the
1296 second is used first to do an initial check, making use of any IP value
1297 restrictions that are set. If there is a match, the first domain is used,
1298 without any IP value restrictions, to get the TXT record.
1300 6. All authenticators now have a server_condition option.
1302 7. There is a new command-line option called -Mset. It is useful only in
1303 conjunction with -be (that is, when testing string expansions). It must be
1304 followed by a message id; Exim loads the given message from its spool
1305 before doing the expansions.
1307 8. Another similar new command-line option is called -bem. It operates like
1308 -be except that it must be followed by the name of a file that contains a
1311 9. When an address is delayed because of a 4xx response to a RCPT command, it
1312 is now the combination of sender and recipient that is delayed in
1313 subsequent queue runs until its retry time is reached.
1315 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1316 shift, have been added to the eval: and eval10: expansion items.
1318 11. The variables $interface_address and $interface_port have been renamed
1319 as $received_ip_address and $received_port, to make it clear that they
1320 relate to message reception rather than delivery. (The old names remain
1321 available for compatibility.)
1323 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1324 to vary the message that is sent when an SMTP command is accepted.
1330 1. There is a new Boolean option called filter_prepend_home for the redirect
1333 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1334 start of receiving a non-SMTP message, before any of the message has been
1337 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1338 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1339 start of the message for an SMTP error code.
1341 4. There is a new parameter for LDAP lookups called "referrals", which takes
1342 one of the settings "follow" (the default) or "nofollow".
1344 5. Version 20070721.2 of exipick now included, offering these new options:
1346 After all other sorting options have bee processed, reverse order
1347 before displaying messages (-R is synonym).
1349 Randomize order of matching messages before displaying.
1351 Instead of displaying the matching messages, display the sum
1353 --sort <variable>[,<variable>...]
1354 Before displaying matching messages, sort the messages according to
1355 each messages value for each variable.
1357 Negate the value for every test (returns inverse output from the
1358 same criteria without --not).
1364 1. The ${readsocket expansion item now supports Internet domain sockets as well
1365 as Unix domain sockets. If the first argument begins "inet:", it must be of
1366 the form "inet:host:port". The port is mandatory; it may be a number or the
1367 name of a TCP port in /etc/services. The host may be a name, or it may be an
1368 IP address. An ip address may optionally be enclosed in square brackets.
1369 This is best for IPv6 addresses. For example:
1371 ${readsocket{inet:[::1]:1234}{<request data>}...
1373 Only a single host name may be given, but if looking it up yield more than
1374 one IP address, they are each tried in turn until a connection is made. Once
1375 a connection has been made, the behaviour is as for ${readsocket with a Unix
1378 2. If a redirect router sets up file or pipe deliveries for more than one
1379 incoming address, and the relevant transport has batch_max set greater than
1380 one, a batch delivery now occurs.
1382 3. The appendfile transport has a new option called maildirfolder_create_regex.
1383 Its value is a regular expression. For a maildir delivery, this is matched
1384 against the maildir directory; if it matches, Exim ensures that a
1385 maildirfolder file is created alongside the new, cur, and tmp directories.
1391 The documentation is up-to-date for the 4.61 release. Major new features since
1392 the 4.60 release are:
1394 . An option called disable_ipv6, to disable the use of IPv6 completely.
1396 . An increase in the number of ACL variables to 20 of each type.
1398 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1399 $2, $3, (though those are still set) because the numeric variables get used
1400 for other things in complicated expansions.
1402 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1404 . It is possible to use setclassresources() on some BSD OS to control the
1405 resources used in pipe deliveries.
1407 . A new ACL modifier called add_header, which can be used with any verb.
1409 . More errors are detectable in retry rules.
1411 There are a number of other additions too.
1417 The documentation is up-to-date for the 4.60 release. Major new features since
1418 the 4.50 release are:
1420 . Support for SQLite.
1422 . Support for IGNOREQUOTA in LMTP.
1424 . Extensions to the "submission mode" features.
1426 . Support for Client SMTP Authorization (CSA).
1428 . Support for ratelimiting hosts and users.
1430 . New expansion items to help with the BATV "prvs" scheme.
1432 . A "match_ip" condition, that matches an IP address against a list.
1434 There are many more minor changes.