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