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