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