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. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
13 list when there are multiple headers having a given name. This matters
14 when individual headers are wrapped onto multiple lines; with previous
15 facilities hard to parse.
17 2. The ${readsocket } expansion item now takes a "tls" option, doing the
20 3. EXPERIMENTAL_REQUIRETLS. See the experimental.spec file.
22 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
24 5. A "pipelining" log_selector.
26 6. Builtin macros for supported log_selector values.
31 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
32 version 3.5.6 or later.
34 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
35 OpenSSL versions are moved to mainline support from Experimental.
36 New SMTP transport option "dane_require_tls_ciphers".
38 3. Feature macros for the compiled-in set of malware scanner interfaces.
40 4. SPF support is promoted from Experimental to mainline status. The template
41 src/EDITME makefile does not enable its inclusion.
43 5. Logging control for DKIM verification. The existing DKIM log line is
44 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
45 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
46 a "dkim" log_selector.
48 6. Receive duration on <= lines, under a new log_selector "receive_time".
50 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
51 routing rules in the manualroute router.
53 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
54 under OpenSSL version 1.1.1 or later.
56 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
57 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
59 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
62 11. "exim -bP macro <name>" returns caller-usable status.
64 12. Expansion item ${authresults {<machine>}} for creating an
65 Authentication-Results: header.
67 13. EXPERIMENTAL_ARC. See the experimental.spec file.
68 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
70 14: A dane:fail event, intended to facilitate reporting.
72 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
73 contain all the servers in the cluster, all of which must be reachable from
74 the running exim instance. If the cluster has master/slave replication, the
75 list must contain all the master and slave servers.
77 16. Add an option to the Avast scanner interface: "pass_unscanned". This
78 allows to treat unscanned files as clean. Files may be unscanned for
79 several reasons: decompression bombs, broken archives.
85 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
86 wildcards will be expanded, values are collapsed.
88 2. The ${readsocket } expansion now takes an option to not shutdown the
89 connection after sending the query string. The default remains to do so.
91 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
92 deliveries on a single TCP connection can maintain a TLS connection
93 open. By default disabled for all hosts, doing so saves the cost of
94 making new TLS sessions, at the cost of having to proxy the data via
95 another process. Logging is also affected.
97 4. A malware connection type for the FPSCAND protocol.
99 5. An option for recipient verify callouts to hold the connection open for
100 further recipients and for delivery.
102 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
105 7. Optionally, an alternate format for spool data-files which matches the
106 wire format - meaning more efficient reception and transmission (at the
107 cost of difficulty with standard Unix tools). Only used for messages
108 received using the ESMTP CHUNKING option, and when a new main-section
109 option "spool_wireformat" (false by default) is set.
111 8. New main configuration option "commandline_checks_require_admin" to
112 restrict who can use various introspection options.
114 9. New option modifier "no_check" for quota and quota_filecount
115 appendfile transport.
117 10. Variable $smtp_command_history returning a comma-sep list of recent
120 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
121 log elements QT, DT and D, and timstamps in debug output.
123 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
124 while still in SYN_RECV state; as a client logs when the connection
125 is opened with a TFO cookie.
127 13. DKIM support for multiple signing, by domain and/or key-selector.
128 DKIM support for multiple hashes, and for alternate-identity tags.
129 Builtin macro with default list of signed headers.
130 Better syntax for specifying oversigning.
131 The DKIM ACL can override verification status, and status is visible in
134 14. Exipick understands -C|--config for an alternative Exim
137 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
138 for ${readsocket } expansions, and for ClamAV.
140 16. The "-be" expansion test mode now supports macros. Macros are expanded
141 in test lines, and new macros can be defined.
143 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
149 1. Allow relative config file names for ".include"
151 2. A main-section config option "debug_store" to control the checks on
152 variable locations during store-reset. Normally false but can be enabled
153 when a memory corrution issue is suspected on a production system.
159 1. The new perl_taintmode option allows to run the embedded perl
160 interpreter in taint mode.
162 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
164 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
167 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
168 N can be 224, 256 (default), 384, 512.
169 With GnuTLS 3.5.0 or later, only.
171 5. Facility for named queues: A command-line argument can specify
172 the queue name for a queue operation, and an ACL modifier can set
173 the queue to be used for a message. A $queue_name variable gives
176 6. New expansion operators base32/base32d.
178 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
179 performance increase and network load decrease. Main config option
180 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
183 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
185 9. Expansion operator escape8bit, like escape but not touching newline etc..
187 10. Feature macros, generated from compile options. All start with "_HAVE_"
188 and go on with some roughly recognisable name. Driver macros, for
189 router, transport and authentication drivers; names starting with "_DRIVER_".
190 Option macros, for each configuration-file option; all start with "_OPT_".
191 Use the "-bP macros" command-line option to see what is present.
193 11. Integer values for options can take a "G" multiplier.
195 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
196 returns from the target back to the initiator, rather than spooling the
199 13. New built-in constants available for tls_dhparam and default changed.
201 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
202 out copies of the message spool files for use by 3rd-party scanners.
204 15. A new option on the smtp transport, hosts_try_fastopen. If the system
205 supports it (on Linux it must be enabled in the kernel by the sysadmin)
206 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
207 but it permits a peer that also supports the facility to send its SMTP
208 banner immediately after the SYN,ACK segment rather then waiting for
209 another ACK - so saving up to one roundtrip time. Because it requires
210 previous communication with the peer (we save a cookie from it) this
211 will only become active on frequently-contacted destinations.
213 16. A new syslog_pid option to suppress PID duplication in syslog lines.
219 1. The ACL conditions regex and mime_regex now capture substrings
220 into numeric variables $regex1 to 9, like the "match" expansion condition.
222 2. New $callout_address variable records the address used for a spam=,
223 malware= or verify= callout.
225 3. Transports now take a "max_parallel" option, to limit concurrency.
227 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
228 The latter expands to a 8-element colon-sep set of hex digits including
229 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
230 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
231 The former operator strips leading zeroes and collapses the longest
232 set of 0-groups to a double-colon.
234 5. New "-bP config" support, to dump the effective configuration.
236 6. New $dkim_key_length variable.
238 7. New base64d and base64 expansion items (the existing str2b64 being a
239 synonym of the latter). Add support in base64 for certificates.
241 8. New main configuration option "bounce_return_linesize_limit" to
242 avoid oversize bodies in bounces. The default value matches RFC
245 9. New $initial_cwd expansion variable.
251 1. Support for using the system standard CA bundle.
253 2. New expansion items $config_file, $config_dir, containing the file
254 and directory name of the main configuration file. Also $exim_version.
256 3. New "malware=" support for Avast.
258 4. New "spam=" variant option for Rspamd.
260 5. Assorted options on malware= and spam= scanners.
262 6. A command-line option to write a comment into the logfile.
264 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
265 be configured to make connections via socks5 proxies.
267 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
268 the transmission of UTF-8 envelope addresses.
270 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
271 used encoding of Maildir folder names.
273 10. A logging option for slow DNS lookups.
275 11. New ${env {<variable>}} expansion.
277 12. A non-SMTP authenticator using information from TLS client certificates.
279 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
280 Patch originally by Wolfgang Breyha.
282 14. Main option "dns_trust_aa" for trusting your local nameserver at the
283 same level as DNSSEC.
289 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
290 DANE SMTP draft to assess a secure chain of trust of the certificate
291 used to establish the TLS connection based on a TLSA record in the
292 domain of the sender.
294 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
295 and several new events have been created. The reason is because it has
296 been expanded beyond just firing events during the transport phase. Any
297 existing TPDA transport options will have to be rewritten to use a new
298 $event_name expansion variable in a condition. Refer to the
299 experimental-spec.txt for details and examples.
301 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
302 server certs used for TLS match the result of the MX lookup. It does
303 not use the same mechanism as DANE.
313 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
314 configured to expect an initial header from a proxy that will make the
315 actual external source IP:host be used in exim instead of the IP of the
316 proxy that is connecting to it.
318 2. New verify option header_names_ascii, which will check to make sure
319 there are no non-ASCII characters in header names. Exim itself handles
320 those non-ASCII characters, but downstream apps may not, so Exim can
321 detect and reject if those characters are present.
323 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
324 codepoints with valid ones.
326 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
327 command line and matching a regex against the return data for trigger
328 and a second regex to extract malware_name. The mail spoolfile name can
329 be included in the command line.
331 5. The smtp transport now supports options "tls_verify_hosts" and
332 "tls_try_verify_hosts". If either is set the certificate verification
333 is split from the encryption operation. The default remains that a failed
334 verification cancels the encryption.
336 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
337 lookup can now set a list of servers to use that is different from the
340 7. New command-line option -C for exiqgrep to specify alternate exim.conf
341 file when searching the queue.
343 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
345 9. Support for DNSSEC on outbound connections.
347 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
348 "certextract" to extract fields from them. Hash operators md5 and sha1
349 work over them for generating fingerprints, and a new sha256 operator
352 11. PRDR is now supported dy default.
354 12. OCSP stapling is now supported by default.
356 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
357 Delivery Status Notification messages in MIME format, and negotiate
358 DSN features per RFC 3461.
364 1. New command-line option -bI:sieve will list all supported sieve extensions
365 of this Exim build on standard output, one per line.
366 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
367 query this to establish the correct list to include in the protocol's
368 SIEVE capability line.
370 2. If the -n option is combined with the -bP option, then the name of an
371 emitted option is not output, only the value (if visible to you).
372 For instance, "exim -n -bP pid_file_path" should just emit a pathname
373 followed by a newline, and no other text.
375 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
376 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
377 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
378 acceptable for security. (Option accepted but ignored if using OpenSSL).
379 Defaults to 1024, the old value. May be lowered only to 512, or raised as
380 far as you like. Raising this may hinder TLS interoperability with other
381 sites and is not currently recommended. Lowering this will permit you to
382 establish a TLS session which is not as secure as you might like.
384 Unless you really know what you are doing, leave it alone.
386 4. If not built with DISABLE_DNSSEC, Exim now has the main option
387 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
388 to send the DO flag to your recursive resolver. If you have a recursive
389 resolver, which can set the Authenticated Data (AD) flag in results, Exim
390 can now detect this. Exim does not perform validation itself, instead
391 relying upon a trusted path to the resolver.
393 Current status: work-in-progress; $sender_host_dnssec variable added.
395 5. DSCP support for outbound connections: on a transport using the smtp driver,
396 set "dscp = ef", for instance, to cause the connections to have the relevant
397 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
399 Similarly for inbound connections, there is a new control modifier, dscp,
400 so "warn control = dscp/ef" in the connect ACL, or after authentication.
402 Supported values depend upon system libraries. "exim -bI:dscp" to list the
403 ones Exim knows of. You can also set a raw number 0..0x3F.
405 6. The -G command-line flag is no longer ignored; it is now equivalent to an
406 ACL setting "control = suppress_local_fixups". The -L command-line flag
407 is now accepted and forces use of syslog, with the provided tag as the
408 process name. A few other flags used by Sendmail are now accepted and
411 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
412 ACL modifier; works for single-recipient mails which are received on and
413 deliverable via SMTP. Using the connection made for a recipient verify,
414 if requested before the verify, or a new one made for the purpose while
415 the inbound connection is still active. The bulk of the mail item is copied
416 direct from the inbound socket to the outbound (as well as the spool file).
417 When the source notifies the end of data, the data acceptance by the destination
418 is negotiated before the acceptance is sent to the source. If the destination
419 does not accept the mail item, for example due to content-scanning, the item
420 is not accepted from the source and therefore there is no need to generate
421 a bounce mail. This is of benefit when providing a secondary-MX service.
422 The downside is that delays are under the control of the ultimate destination
425 The Received-by: header on items delivered by cutthrough is generated
426 early in reception rather than at the end; this will affect any timestamp
427 included. The log line showing delivery is recorded before that showing
428 reception; it uses a new ">>" tag instead of "=>".
430 To support the feature, verify-callout connections can now use ESMTP and TLS.
431 The usual smtp transport options are honoured, plus a (new, default everything)
432 hosts_verify_avoid_tls.
434 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
435 for specific access to the information for each connection. The old names
436 are present for now but deprecated.
438 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
440 8. New expansion operators ${listnamed:name} to get the content of a named list
441 and ${listcount:string} to count the items in a list.
443 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
444 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
445 modules. For some situations this is desirable, but we expect admin in
446 those situations to know they want the feature. More commonly, it means
447 that GUI user modules get loaded and are broken by the setuid Exim being
448 unable to access files specified in environment variables and passed
449 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
450 unless this new option is set.
452 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
453 so have also added a build option which can be used to build Exim with GnuTLS
454 but without trying to use any kind of PKCS11 support. Uncomment this in the
457 AVOID_GNUTLS_PKCS11=yes
459 10. The "acl = name" condition on an ACL now supports optional arguments.
460 New expansion item "${acl {name}{arg}...}" and expansion condition
461 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
462 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
463 Variable $acl_narg contains the number of arguments. If the ACL sets
464 a "message =" value this becomes the result of the expansion item,
465 or the value of $value for the expansion condition. If the ACL returns
466 accept the expansion condition is true; if reject, false. A defer
467 return results in a forced fail.
469 11. Routers and transports can now have multiple headers_add and headers_remove
470 option lines. The concatenated list is used.
472 12. New ACL modifier "remove_header" can remove headers before message gets
473 handled by routers/transports.
475 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
476 "aaaa" and "a" lookups is done and the full set of results returned.
478 14. New expansion variable $headers_added with content from ACL add_header
479 modifier (but not yet added to message).
481 15. New 8bitmime status logging option for received messages. Log field "M8S".
483 16. New authenticated_sender logging option, adding to log field "A".
485 17. New expansion variables $router_name and $transport_name. Useful
486 particularly for debug_print as -bt command-line option does not
487 require privilege whereas -d does.
489 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
490 proposed extension to SMTP from Eric Hall.
492 19. The pipe transport has gained the force_command option, to allow
493 decorating commands from user .forward pipe aliases with prefix
494 wrappers, for instance.
496 20. Callout connections can now AUTH; the same controls as normal delivery
499 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
500 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
501 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
502 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
503 dmarc_status. It adds new control flags dmarc_disable_verify and
504 dmarc_enable_forensic. The default for the dmarc_tld_file option is
505 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
507 22. Add expansion variable $authenticated_fail_id, which is the username
508 provided to the authentication method which failed. It is available
509 for use in subsequent ACL processing (typically quit or notquit ACLs).
511 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
514 24. New ${hexquote:..string..} expansion operator converts non-printable
515 characters in the string to \xNN form.
517 25. Experimental TPDA (Transport Post Delivery Action) function added.
518 Patch provided by Axel Rau.
520 26. Experimental Redis lookup added. Patch provided by Warren Baker.
526 1. New authenticator driver, "gsasl". Server-only (at present).
527 This is a SASL interface, licensed under GPL, which can be found at
528 http://www.gnu.org/software/gsasl/.
529 This system does not provide sources of data for authentication, so
530 careful use needs to be made of the conditions in Exim.
532 2. New authenticator driver, "heimdal_gssapi". Server-only.
533 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
534 is no longer honoured for setuid programs by Heimdal. Use the
535 "server_keytab" option to point to the keytab.
537 3. The "pkg-config" system can now be used when building Exim to reference
538 cflags and library information for lookups and authenticators, rather
539 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
540 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
541 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
543 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
544 find the headers and libraries for PCRE.
546 4. New expansion variable $tls_bits.
548 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
549 be joined together with ASCII NUL characters to construct the key to pass
550 into the DBM library. Can be used with gsasl to access sasldb2 files as
553 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
555 Avoid release 1.0.1a if you can. Note that the default value of
556 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
557 increased susceptibility to attack. This may still have interoperability
558 implications for very old clients (see version 4.31 change 37) but
559 administrators can choose to make the trade-off themselves and restore
560 compatibility at the cost of session security.
562 7. Use of the new expansion variable $tls_sni in the main configuration option
563 tls_certificate will cause Exim to re-expand the option, if the client
564 sends the TLS Server Name Indication extension, to permit choosing a
565 different certificate; tls_privatekey will also be re-expanded. You must
566 still set these options to expand to valid files when $tls_sni is not set.
568 The SMTP Transport has gained the option tls_sni, which will set a hostname
569 for outbound TLS sessions, and set $tls_sni too.
571 A new log_selector, +tls_sni, has been added, to log received SNI values
572 for Exim as a server.
574 8. The existing "accept_8bitmime" option now defaults to true. This means
575 that Exim is deliberately not strictly RFC compliant. We're following
576 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
577 Those who disagree, or know that they are talking to mail servers that,
578 even today, are not 8-bit clean, need to turn off this option.
580 9. Exim can now be started with -bw (with an optional timeout, given as
581 -bw<timespec>). With this, stdin at startup is a socket that is
582 already listening for connections. This has a more modern name of
583 "socket activation", but forcing the activated socket to fd 0. We're
584 interested in adding more support for modern variants.
586 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
587 for numbers indicates multiplication by 1024^3.
589 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
590 gnutls_require_mac & gnutls_require_protocols are no longer supported.
591 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
592 string, documentation for which is at:
593 http://www.gnutls.org/manual/html_node/Priority-Strings.html
595 SNI support has been added to Exim's GnuTLS integration too.
597 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
598 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
600 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
601 is now available. If the contents of the file are valid, then Exim will
602 send that back in response to a TLS status request; this is OCSP Stapling.
603 Exim will not maintain the contents of the file in any way: administrators
604 are responsible for ensuring that it is up-to-date.
606 See "experimental-spec.txt" for more details.
608 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
609 identically to TXT record lookups.
611 14. New expansion variable $tod_epoch_l for higher-precision time.
613 15. New global option tls_dh_max_bits, defaulting to current value of NSS
614 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
615 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
617 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
618 Option can now be a path or an identifier for a standard prime.
619 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
620 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
623 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
624 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
625 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
631 1. New options for the ratelimit ACL condition: /count= and /unique=.
632 The /noupdate option has been replaced by a /readonly option.
634 2. The SMTP transport's protocol option may now be set to "smtps", to
635 use SSL-on-connect outbound.
637 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
638 there is a problem talking to the AV scanner, or the AV scanner running.
640 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
641 and check if the search item is a member of the list. This does not
642 support named lists, but does subject the list part to string expansion.
644 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
645 built, Exim no longer performs string expansion on the second string of
646 the match_* expansion conditions: "match_address", "match_domain",
647 "match_ip" & "match_local_part". Named lists can still be used.
653 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
654 or off in the resolver library.
660 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
661 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
662 libraries. The following global options have been added in support of
663 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
664 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
666 2. The pipe transport now takes a boolean option, "freeze_signal", default
667 false. When true, if the external delivery command exits on a signal then
668 Exim will freeze the message in the queue, instead of generating a bounce.
670 3. Log filenames may now use %M as an escape, instead of %D (still available).
671 The %M pattern expands to yyyymm, providing month-level resolution.
673 4. The $message_linecount variable is now updated for the maildir_tag option,
674 in the same way as $message_size, to reflect the real number of lines,
675 including any header additions or removals from transport.
677 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
678 Exim now selects entries randomly, to better scale in a cluster setup.
684 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
685 the flaw permitted the Exim run-time user to cause root to append to
686 arbitrary files of the attacker's choosing, with the content based
687 on content supplied by the attacker.
689 2. Exim now supports loading some lookup types at run-time, using your
690 platform's dlopen() functionality. This has limited platform support
691 and the intention is not to support every variant, it's limited to
692 dlopen(). This permits the main Exim binary to not be linked against
693 all the libraries needed for all the lookup types.
699 NOTE: this version is not guaranteed backwards-compatible, please read the
700 items below carefully
702 1. A new main configuration option, "openssl_options", is available if Exim
703 is built with SSL support provided by OpenSSL. The option allows
704 administrators to specify OpenSSL options to be used on connections;
705 typically this is to set bug compatibility features which the OpenSSL
706 developers have not enabled by default. There may be security
707 consequences for certain options, so these should not be changed
710 2. A new pipe transport option, "permit_coredumps", may help with problem
711 diagnosis in some scenarios. Note that Exim is typically installed as
712 a setuid binary, which on most OSes will inhibit coredumps by default,
713 so that safety mechanism would have to be overridden for this option to
714 be able to take effect.
716 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
717 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
718 Note that this switches Exim to use a new API ("INSTREAM") and a future
719 release of ClamAV will remove support for the old API ("STREAM").
721 The av_scanner option, when set to "clamd", now takes an optional third
722 part, "local", which causes Exim to pass a filename to ClamAV instead of
723 the file content. This is the same behaviour as when clamd is pointed at
724 a Unix-domain socket. For example:
726 av_scanner = clamd:192.0.2.3 1234:local
728 ClamAV's ExtendedDetectionInfo response format is now handled.
730 4. There is now a -bmalware option, restricted to admin users. This option
731 takes one parameter, a filename, and scans that file with Exim's
732 malware-scanning framework. This is intended purely as a debugging aid
733 to ensure that Exim's scanning is working, not to replace other tools.
734 Note that the ACL framework is not invoked, so if av_scanner references
735 ACL variables without a fallback then this will fail.
737 5. There is a new expansion operator, "reverse_ip", which will reverse IP
738 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
740 ${reverse_ip:192.0.2.4}
742 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
743 -> 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
745 6. There is a new ACL control called "debug", to enable debug logging.
746 This allows selective logging of certain incoming transactions within
747 production environments, with some care. It takes two options, "tag"
748 and "opts"; "tag" is included in the filename of the log and "opts"
749 is used as per the -d<options> command-line option. Examples, which
750 don't all make sense in all contexts:
753 control = debug/tag=.$sender_host_address
754 control = debug/opts=+expand+acl
755 control = debug/tag=.$message_exim_id/opts=+expand
757 7. It has always been implicit in the design and the documentation that
758 "the Exim user" is not root. src/EDITME said that using root was
759 "very strongly discouraged". This is not enough to keep people from
760 shooting themselves in the foot in days when many don't configure Exim
761 themselves but via package build managers. The security consequences of
762 running various bits of network code are severe if there should be bugs in
763 them. As such, the Exim user may no longer be root. If configured
764 statically, Exim will refuse to build. If configured as ref:user then Exim
765 will exit shortly after start-up. If you must shoot yourself in the foot,
766 then henceforth you will have to maintain your own local patches to strip
769 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
770 condition logic to determine truth/failure and will fail to expand many
771 strings, bool_lax{} uses the router condition logic, where most strings
773 Note: bool{00} is false, bool_lax{00} is true.
775 9. Routers now support multiple "condition" tests.
777 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
778 Setting this allows an admin to define which entry in the tcpwrappers
779 config file will be used to control access to the daemon. This option
780 is only available when Exim is built with USE_TCP_WRAPPERS. The
781 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
784 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
785 the Exim run-time user, instead of root.
787 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
788 is forced on. This is mitigated by the new build option
789 TRUSTED_CONFIG_LIST which defines a list of configuration files which
790 are trusted; one per line. If a config file is owned by root and matches
791 a pathname in the list, then it may be invoked by the Exim build-time
792 user without Exim relinquishing root privileges.
794 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
795 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
796 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
797 include the main config. As a transition mechanism, we are temporarily
798 providing a work-around: the new build option WHITELIST_D_MACROS provides
799 a colon-separated list of macro names which may be overridden by the Exim
800 run-time user. The values of these macros are constrained to the regex
801 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
807 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
808 writable, the other to locking of MBX folders (not mbox).
810 2. MySQL stored procedures are now supported.
812 3. The dkim_domain transport option is now a list, not a single string, and
813 messages will be signed for each element in the list (discarding
816 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
817 in the presence of multiple character strings within the RR. Prior to 4.70,
818 only the first string would be returned. The dnsdb lookup now, by default,
819 preserves the pre-4.70 semantics, but also now takes an extended output
820 separator specification. The separator can be followed by a semicolon, to
821 concatenate the individual text strings together with no join character,
822 or by a comma and a second separator character, in which case the text
823 strings within a TXT record are joined on that second character.
824 Administrators are reminded that DNS provides no ordering guarantees
825 between multiple records in an RRset. For example:
827 foo.example. IN TXT "a" "b" "c"
828 foo.example. IN TXT "d" "e" "f"
830 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
831 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
832 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
838 1. Native DKIM support without an external library.
839 (Note that if no action to prevent it is taken, a straight upgrade will
840 result in DKIM verification of all signed incoming emails. See spec
841 for details on conditionally disabling)
843 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
845 3. There is now a bool{} expansion condition which maps certain strings to
846 true/false condition values (most likely of use in conjunction with the
847 and{} expansion operator).
849 4. The $spam_score, $spam_bar and $spam_report variables are now available
852 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
853 options, provided that Exim is invoked by an admin_user.
855 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
856 which increases compatibility with older clients at the cost of decreased
857 security. Don't set this unless you need to support such clients.
859 7. There is a new expansion operator, ${randint:...} which will produce a
860 "random" number less than the supplied integer. This randomness is
861 not guaranteed to be cryptographically strong, but depending upon how
862 Exim was built may be better than the most naive schemes.
864 8. Exim now explicitly ensures that SHA256 is available when linked against
867 9. The transport_filter_timeout option now applies to SMTP transports too.
873 1. Preliminary DKIM support in Experimental.
879 1. The body_linecount and body_zerocount C variables are now exported in the
882 2. When a dnslists lookup succeeds, the key that was looked up is now placed
883 in $dnslist_matched. When the key is an IP address, it is not reversed in
884 this variable (though it is, of course, in the actual lookup). In simple
887 deny dnslists = spamhaus.example
889 the key is also available in another variable (in this case,
890 $sender_host_address). In more complicated cases, however, this is not
891 true. For example, using a data lookup might generate a dnslists lookup
894 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
896 If this condition succeeds, the value in $dnslist_matched might be
897 192.168.6.7 (for example).
899 3. Authenticators now have a client_condition option. When Exim is running as
900 a client, it skips an authenticator whose client_condition expansion yields
901 "0", "no", or "false". This can be used, for example, to skip plain text
902 authenticators when the connection is not encrypted by a setting such as:
904 client_condition = ${if !eq{$tls_cipher}{}}
906 Note that the 4.67 documentation states that $tls_cipher contains the
907 cipher used for incoming messages. In fact, during SMTP delivery, it
908 contains the cipher used for the delivery. The same is true for
911 4. There is now a -Mvc <message-id> option, which outputs a copy of the
912 message to the standard output, in RFC 2822 format. The option can be used
913 only by an admin user.
915 5. There is now a /noupdate option for the ratelimit ACL condition. It
916 computes the rate and checks the limit as normal, but it does not update
917 the saved data. This means that, in relevant ACLs, it is possible to lookup
918 the existence of a specified (or auto-generated) ratelimit key without
919 incrementing the ratelimit counter for that key.
921 In order for this to be useful, another ACL entry must set the rate
922 for the same key somewhere (otherwise it will always be zero).
927 # Read the rate; if it doesn't exist or is below the maximum
929 deny ratelimit = 100 / 5m / strict / noupdate
930 log_message = RATE: $sender_rate / $sender_rate_period \
931 (max $sender_rate_limit)
933 [... some other logic and tests...]
935 warn ratelimit = 100 / 5m / strict / per_cmd
936 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
937 (max $sender_rate_limit)
938 condition = ${if le{$sender_rate}{$sender_rate_limit}}
942 6. The variable $max_received_linelength contains the number of bytes in the
943 longest line that was received as part of the message, not counting the
944 line termination character(s).
946 7. Host lists can now include +ignore_defer and +include_defer, analagous to
947 +ignore_unknown and +include_unknown. These options should be used with
948 care, probably only in non-critical host lists such as whitelists.
950 8. There's a new option called queue_only_load_latch, which defaults true.
951 If set false when queue_only_load is greater than zero, Exim re-evaluates
952 the load for each incoming message in an SMTP session. Otherwise, once one
953 message is queued, the remainder are also.
955 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
956 cases when an SMTP session ends without sending QUIT. However, when Exim
957 itself is is bad trouble, such as being unable to write to its log files,
958 this ACL is not run, because it might try to do things (such as write to
959 log files) that make the situation even worse.
961 Like the QUIT ACL, this new ACL is provided to make it possible to gather
962 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
963 modifier is forbidden in this ACL.
965 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
966 to a string that indicates the reason for the termination of the SMTP
967 connection. The possible values are:
969 acl-drop Another ACL issued a "drop" command
970 bad-commands Too many unknown or non-mail commands
971 command-timeout Timeout while reading SMTP commands
972 connection-lost The SMTP connection has been lost
973 data-timeout Timeout while reading message data
974 local-scan-error The local_scan() function crashed
975 local-scan-timeout The local_scan() function timed out
976 signal-exit SIGTERM or SIGINT
977 synchronization-error SMTP synchronization error
978 tls-failed TLS failed to start
980 In most cases when an SMTP connection is closed without having received
981 QUIT, Exim sends an SMTP response message before actually closing the
982 connection. With the exception of acl-drop, the default message can be
983 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
984 "drop" verb in another ACL, it is the message from the other ACL that is
987 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
988 servers with individual queries. This is done by starting the query with
989 "servers=x:y:z;", where each item in the list may take one of two forms:
991 (1) If it is just a host name, the appropriate global option (mysql_servers
992 or pgsql_servers) is searched for a host of the same name, and the
993 remaining parameters (database, user, password) are taken from there.
995 (2) If it contains any slashes, it is taken as a complete parameter set.
997 The list of servers is used in exactly the same was as the global list.
998 Once a connection to a server has happened and a query has been
999 successfully executed, processing of the lookup ceases.
1001 This feature is intended for use in master/slave situations where updates
1002 are occurring, and one wants to update a master rather than a slave. If the
1003 masters are in the list for reading, you might have:
1005 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1007 In an updating lookup, you could then write
1009 ${lookup mysql{servers=master; UPDATE ...}
1011 If, on the other hand, the master is not to be used for reading lookups:
1013 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1015 you can still update the master by
1017 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1019 11. The message_body_newlines option (default FALSE, for backwards
1020 compatibility) can be used to control whether newlines are present in
1021 $message_body and $message_body_end. If it is FALSE, they are replaced by
1028 1. There is a new log selector called smtp_no_mail, which is not included in
1029 the default setting. When it is set, a line is written to the main log
1030 whenever an accepted SMTP connection terminates without having issued a
1033 2. When an item in a dnslists list is followed by = and & and a list of IP
1034 addresses, the behaviour was not clear when the lookup returned more than
1035 one IP address. This has been solved by the addition of == and =& for "all"
1036 rather than the default "any" matching.
1038 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1039 for the cipher algorithms. New options have been added to allow some of the
1040 other parameters to be varied.
1042 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1043 set, Exim compiles a runtime option called disable_fsync.
1045 5. There is a new variable called $smtp_count_at_connection_start.
1047 6. There's a new control called no_pipelining.
1049 7. There are two new variables called $sending_ip_address and $sending_port.
1050 These are set whenever an SMTP connection to another host has been set up.
1052 8. The expansion of the helo_data option in the smtp transport now happens
1053 after the connection to the server has been made.
1055 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1056 are encoded as per RFC 2047.
1058 10. There is a new log selector called "pid", which causes the current process
1059 id to be added to every log line, in square brackets, immediately after the
1062 11. Exim has been modified so that it flushes SMTP output before implementing
1063 a delay in an ACL. It also flushes the output before performing a callout,
1064 as this can take a substantial time. These behaviours can be disabled by
1065 obeying control = no_delay_flush or control = no_callout_flush,
1066 respectively, at some earlier stage of the connection.
1068 12. There are two new expansion conditions that iterate over a list. They are
1069 called forany and forall.
1071 13. There's a new global option called dsn_from that can be used to vary the
1072 contents of From: lines in bounces and other automatically generated
1073 messages ("delivery status notifications" - hence the name of the option).
1075 14. The smtp transport has a new option called hosts_avoid_pipelining.
1077 15. By default, exigrep does case-insensitive matches. There is now a -I option
1078 that makes it case-sensitive.
1080 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1081 been added to string expansions to make it easier to process lists of
1082 items, typically addresses.
1084 17. There's a new ACL modifier called "continue". It does nothing of itself,
1085 and processing of the ACL always continues with the next condition or
1086 modifier. It is provided so that the side effects of expanding its argument
1089 18. It is now possible to use newline and other control characters (those with
1090 values less than 32, plus DEL) as separators in lists.
1092 19. The exigrep utility now has a -v option, which inverts the matching
1095 20. The host_find_failed option in the manualroute router can now be set to
1102 No new features were added to 4.66.
1108 No new features were added to 4.65.
1114 1. ACL variables can now be given arbitrary names, as long as they start with
1115 "acl_c" or "acl_m" (for connection variables and message variables), are at
1116 least six characters long, with the sixth character being either a digit or
1119 2. There is a new ACL modifier called log_reject_target. It makes it possible
1120 to specify which logs are used for messages about ACL rejections.
1122 3. There is a new authenticator called "dovecot". This is an interface to the
1123 authentication facility of the Dovecot POP/IMAP server, which can support a
1124 number of authentication methods.
1126 4. The variable $message_headers_raw provides a concatenation of all the
1127 messages's headers without any decoding. This is in contrast to
1128 $message_headers, which does RFC2047 decoding on the header contents.
1130 5. In a DNS black list, if two domain names, comma-separated, are given, the
1131 second is used first to do an initial check, making use of any IP value
1132 restrictions that are set. If there is a match, the first domain is used,
1133 without any IP value restrictions, to get the TXT record.
1135 6. All authenticators now have a server_condition option.
1137 7. There is a new command-line option called -Mset. It is useful only in
1138 conjunction with -be (that is, when testing string expansions). It must be
1139 followed by a message id; Exim loads the given message from its spool
1140 before doing the expansions.
1142 8. Another similar new command-line option is called -bem. It operates like
1143 -be except that it must be followed by the name of a file that contains a
1146 9. When an address is delayed because of a 4xx response to a RCPT command, it
1147 is now the combination of sender and recipient that is delayed in
1148 subsequent queue runs until its retry time is reached.
1150 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1151 shift, have been added to the eval: and eval10: expansion items.
1153 11. The variables $interface_address and $interface_port have been renamed
1154 as $received_ip_address and $received_port, to make it clear that they
1155 relate to message reception rather than delivery. (The old names remain
1156 available for compatibility.)
1158 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1159 to vary the message that is sent when an SMTP command is accepted.
1165 1. There is a new Boolean option called filter_prepend_home for the redirect
1168 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1169 start of receiving a non-SMTP message, before any of the message has been
1172 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1173 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1174 start of the message for an SMTP error code.
1176 4. There is a new parameter for LDAP lookups called "referrals", which takes
1177 one of the settings "follow" (the default) or "nofollow".
1179 5. Version 20070721.2 of exipick now included, offering these new options:
1181 After all other sorting options have bee processed, reverse order
1182 before displaying messages (-R is synonym).
1184 Randomize order of matching messages before displaying.
1186 Instead of displaying the matching messages, display the sum
1188 --sort <variable>[,<variable>...]
1189 Before displaying matching messages, sort the messages according to
1190 each messages value for each variable.
1192 Negate the value for every test (returns inverse output from the
1193 same criteria without --not).
1199 1. The ${readsocket expansion item now supports Internet domain sockets as well
1200 as Unix domain sockets. If the first argument begins "inet:", it must be of
1201 the form "inet:host:port". The port is mandatory; it may be a number or the
1202 name of a TCP port in /etc/services. The host may be a name, or it may be an
1203 IP address. An ip address may optionally be enclosed in square brackets.
1204 This is best for IPv6 addresses. For example:
1206 ${readsocket{inet:[::1]:1234}{<request data>}...
1208 Only a single host name may be given, but if looking it up yield more than
1209 one IP address, they are each tried in turn until a connection is made. Once
1210 a connection has been made, the behaviour is as for ${readsocket with a Unix
1213 2. If a redirect router sets up file or pipe deliveries for more than one
1214 incoming address, and the relevant transport has batch_max set greater than
1215 one, a batch delivery now occurs.
1217 3. The appendfile transport has a new option called maildirfolder_create_regex.
1218 Its value is a regular expression. For a maildir delivery, this is matched
1219 against the maildir directory; if it matches, Exim ensures that a
1220 maildirfolder file is created alongside the new, cur, and tmp directories.
1226 The documentation is up-to-date for the 4.61 release. Major new features since
1227 the 4.60 release are:
1229 . An option called disable_ipv6, to disable the use of IPv6 completely.
1231 . An increase in the number of ACL variables to 20 of each type.
1233 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1234 $2, $3, (though those are still set) because the numeric variables get used
1235 for other things in complicated expansions.
1237 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1239 . It is possible to use setclassresources() on some BSD OS to control the
1240 resources used in pipe deliveries.
1242 . A new ACL modifier called add_header, which can be used with any verb.
1244 . More errors are detectable in retry rules.
1246 There are a number of other additions too.
1252 The documentation is up-to-date for the 4.60 release. Major new features since
1253 the 4.50 release are:
1255 . Support for SQLite.
1257 . Support for IGNOREQUOTA in LMTP.
1259 . Extensions to the "submission mode" features.
1261 . Support for Client SMTP Authorization (CSA).
1263 . Support for ratelimiting hosts and users.
1265 . New expansion items to help with the BATV "prvs" scheme.
1267 . A "match_ip" condition, that matches an IP address against a list.
1269 There are many more minor changes.
git://git.exim.org / exim.git / blob