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