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. PKG_CONFIG_PATH can now be set in Local/Makefile;
13 wildcards will be expanded, values are collapsed.
15 2. The ${readsocket } expansion now takes an option to not shutdown the
16 connection after sending the query string. The default remains to do so.
18 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
19 deliveries on a single TCP connection can maintain a TLS connection
20 open. By default disabled for all hosts, doing so saves the cost of
21 making new TLS sessions, at the cost of having to proxy the data via
22 another process. Logging is also affected.
24 4. A malware connection type for the FPSCAND protocol.
26 5. An option for recipient verify callouts to hold the connection open for
27 further recipients and for delivery.
29 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
32 7. Optionally, an alternate format for spool data-files which matches the
33 wire format - meaning more efficient reception and transmission (at the
34 cost of difficulty with standard Unix tools). Only used for messages
35 received using the ESMTP CHUNKING option, and when a new main-section
36 option "spool_wireformat" (false by default) is set.
42 1. Allow relative config file names for ".include"
44 2. A main-section config option "debug_store" to control the checks on
45 variable locations during store-reset. Normally false but can be enabled
46 when a memory corrution issue is suspected on a production system.
52 1. The new perl_taintmode option allows to run the embedded perl
53 interpreter in taint mode.
55 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
57 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
60 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
61 N can be 224, 256 (default), 384, 512.
62 With GnuTLS 3.5.0 or later, only.
64 5. Facility for named queues: A command-line argument can specify
65 the queue name for a queue operation, and an ACL modifier can set
66 the queue to be used for a message. A $queue_name variable gives
69 6. New expansion operators base32/base32d.
71 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
72 performance increase and network load decrease. Main config option
73 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
76 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
78 9. Expansion operator escape8bit, like escape but not touching newline etc..
80 10. Feature macros, generated from compile options. All start with "_HAVE_"
81 and go on with some roughly recognisable name. Driver macros, for
82 router, transport and authentication drivers; names starting with "_DRIVER_".
83 Option macros, for each configuration-file option; all start with "_OPT_".
84 Use the "-bP macros" command-line option to see what is present.
86 11. Integer values for options can take a "G" multiplier.
88 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
89 returns from the target back to the initiator, rather than spooling the
92 13. New built-in constants available for tls_dhparam and default changed.
94 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
95 out copies of the message spool files for use by 3rd-party scanners.
97 15. A new option on the smtp transport, hosts_try_fastopen. If the system
98 supports it (on Linux it must be enabled in the kernel by the sysadmin)
99 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
100 but it permits a peer that also supports the facility to send its SMTP
101 banner immediately after the SYN,ACK segment rather then waiting for
102 another ACK - so saving up to one roundtrip time. Because it requires
103 previous communication with the peer (we save a cookie from it) this
104 will only become active on frequently-contacted destinations.
106 16. A new syslog_pid option to suppress PID duplication in syslog lines.
112 1. The ACL conditions regex and mime_regex now capture substrings
113 into numeric variables $regex1 to 9, like the "match" expansion condition.
115 2. New $callout_address variable records the address used for a spam=,
116 malware= or verify= callout.
118 3. Transports now take a "max_parallel" option, to limit concurrency.
120 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
121 The latter expands to a 8-element colon-sep set of hex digits including
122 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
123 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
124 The former operator strips leading zeroes and collapses the longest
125 set of 0-groups to a double-colon.
127 5. New "-bP config" support, to dump the effective configuration.
129 6. New $dkim_key_length variable.
131 7. New base64d and base64 expansion items (the existing str2b64 being a
132 synonym of the latter). Add support in base64 for certificates.
134 8. New main configuration option "bounce_return_linesize_limit" to
135 avoid oversize bodies in bounces. The default value matches RFC
138 9. New $initial_cwd expansion variable.
144 1. Support for using the system standard CA bundle.
146 2. New expansion items $config_file, $config_dir, containing the file
147 and directory name of the main configuration file. Also $exim_version.
149 3. New "malware=" support for Avast.
151 4. New "spam=" variant option for Rspamd.
153 5. Assorted options on malware= and spam= scanners.
155 6. A command-line option to write a comment into the logfile.
157 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
158 be configured to make connections via socks5 proxies.
160 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
161 the transmission of UTF-8 envelope addresses.
163 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
164 used encoding of Maildir folder names.
166 10. A logging option for slow DNS lookups.
168 11. New ${env {<variable>}} expansion.
170 12. A non-SMTP authenticator using information from TLS client certificates.
172 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
173 Patch originally by Wolfgang Breyha.
175 14. Main option "dns_trust_aa" for trusting your local nameserver at the
176 same level as DNSSEC.
182 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
183 DANE SMTP draft to assess a secure chain of trust of the certificate
184 used to establish the TLS connection based on a TLSA record in the
185 domain of the sender.
187 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
188 and several new events have been created. The reason is because it has
189 been expanded beyond just firing events during the transport phase. Any
190 existing TPDA transport options will have to be rewritten to use a new
191 $event_name expansion variable in a condition. Refer to the
192 experimental-spec.txt for details and examples.
194 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
195 server certs used for TLS match the result of the MX lookup. It does
196 not use the same mechanism as DANE.
206 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
207 configured to expect an initial header from a proxy that will make the
208 actual external source IP:host be used in exim instead of the IP of the
209 proxy that is connecting to it.
211 2. New verify option header_names_ascii, which will check to make sure
212 there are no non-ASCII characters in header names. Exim itself handles
213 those non-ASCII characters, but downstream apps may not, so Exim can
214 detect and reject if those characters are present.
216 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
217 codepoints with valid ones.
219 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
220 command line and matching a regex against the return data for trigger
221 and a second regex to extract malware_name. The mail spoolfile name can
222 be included in the command line.
224 5. The smtp transport now supports options "tls_verify_hosts" and
225 "tls_try_verify_hosts". If either is set the certificate verification
226 is split from the encryption operation. The default remains that a failed
227 verification cancels the encryption.
229 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
230 lookup can now set a list of servers to use that is different from the
233 7. New command-line option -C for exiqgrep to specify alternate exim.conf
234 file when searching the queue.
236 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
238 9. Support for DNSSEC on outbound connections.
240 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
241 "certextract" to extract fields from them. Hash operators md5 and sha1
242 work over them for generating fingerprints, and a new sha256 operator
245 11. PRDR is now supported dy default.
247 12. OCSP stapling is now supported by default.
249 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
250 Delivery Status Notification messages in MIME format, and negotiate
251 DSN features per RFC 3461.
257 1. New command-line option -bI:sieve will list all supported sieve extensions
258 of this Exim build on standard output, one per line.
259 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
260 query this to establish the correct list to include in the protocol's
261 SIEVE capability line.
263 2. If the -n option is combined with the -bP option, then the name of an
264 emitted option is not output, only the value (if visible to you).
265 For instance, "exim -n -bP pid_file_path" should just emit a pathname
266 followed by a newline, and no other text.
268 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
269 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
270 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
271 acceptable for security. (Option accepted but ignored if using OpenSSL).
272 Defaults to 1024, the old value. May be lowered only to 512, or raised as
273 far as you like. Raising this may hinder TLS interoperability with other
274 sites and is not currently recommended. Lowering this will permit you to
275 establish a TLS session which is not as secure as you might like.
277 Unless you really know what you are doing, leave it alone.
279 4. If not built with DISABLE_DNSSEC, Exim now has the main option
280 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
281 to send the DO flag to your recursive resolver. If you have a recursive
282 resolver, which can set the Authenticated Data (AD) flag in results, Exim
283 can now detect this. Exim does not perform validation itself, instead
284 relying upon a trusted path to the resolver.
286 Current status: work-in-progress; $sender_host_dnssec variable added.
288 5. DSCP support for outbound connections: on a transport using the smtp driver,
289 set "dscp = ef", for instance, to cause the connections to have the relevant
290 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
292 Similarly for inbound connections, there is a new control modifier, dscp,
293 so "warn control = dscp/ef" in the connect ACL, or after authentication.
295 Supported values depend upon system libraries. "exim -bI:dscp" to list the
296 ones Exim knows of. You can also set a raw number 0..0x3F.
298 6. The -G command-line flag is no longer ignored; it is now equivalent to an
299 ACL setting "control = suppress_local_fixups". The -L command-line flag
300 is now accepted and forces use of syslog, with the provided tag as the
301 process name. A few other flags used by Sendmail are now accepted and
304 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
305 ACL modifier; works for single-recipient mails which are received on and
306 deliverable via SMTP. Using the connection made for a recipient verify,
307 if requested before the verify, or a new one made for the purpose while
308 the inbound connection is still active. The bulk of the mail item is copied
309 direct from the inbound socket to the outbound (as well as the spool file).
310 When the source notifies the end of data, the data acceptance by the destination
311 is negotiated before the acceptance is sent to the source. If the destination
312 does not accept the mail item, for example due to content-scanning, the item
313 is not accepted from the source and therefore there is no need to generate
314 a bounce mail. This is of benefit when providing a secondary-MX service.
315 The downside is that delays are under the control of the ultimate destination
318 The Received-by: header on items delivered by cutthrough is generated
319 early in reception rather than at the end; this will affect any timestamp
320 included. The log line showing delivery is recorded before that showing
321 reception; it uses a new ">>" tag instead of "=>".
323 To support the feature, verify-callout connections can now use ESMTP and TLS.
324 The usual smtp transport options are honoured, plus a (new, default everything)
325 hosts_verify_avoid_tls.
327 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
328 for specific access to the information for each connection. The old names
329 are present for now but deprecated.
331 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
333 8. New expansion operators ${listnamed:name} to get the content of a named list
334 and ${listcount:string} to count the items in a list.
336 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
337 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
338 modules. For some situations this is desirable, but we expect admin in
339 those situations to know they want the feature. More commonly, it means
340 that GUI user modules get loaded and are broken by the setuid Exim being
341 unable to access files specified in environment variables and passed
342 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
343 unless this new option is set.
345 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
346 so have also added a build option which can be used to build Exim with GnuTLS
347 but without trying to use any kind of PKCS11 support. Uncomment this in the
350 AVOID_GNUTLS_PKCS11=yes
352 10. The "acl = name" condition on an ACL now supports optional arguments.
353 New expansion item "${acl {name}{arg}...}" and expansion condition
354 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
355 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
356 Variable $acl_narg contains the number of arguments. If the ACL sets
357 a "message =" value this becomes the result of the expansion item,
358 or the value of $value for the expansion condition. If the ACL returns
359 accept the expansion condition is true; if reject, false. A defer
360 return results in a forced fail.
362 11. Routers and transports can now have multiple headers_add and headers_remove
363 option lines. The concatenated list is used.
365 12. New ACL modifier "remove_header" can remove headers before message gets
366 handled by routers/transports.
368 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
369 "aaaa" and "a" lookups is done and the full set of results returned.
371 14. New expansion variable $headers_added with content from ACL add_header
372 modifier (but not yet added to message).
374 15. New 8bitmime status logging option for received messages. Log field "M8S".
376 16. New authenticated_sender logging option, adding to log field "A".
378 17. New expansion variables $router_name and $transport_name. Useful
379 particularly for debug_print as -bt command-line option does not
380 require privilege whereas -d does.
382 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
383 proposed extension to SMTP from Eric Hall.
385 19. The pipe transport has gained the force_command option, to allow
386 decorating commands from user .forward pipe aliases with prefix
387 wrappers, for instance.
389 20. Callout connections can now AUTH; the same controls as normal delivery
392 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
393 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
394 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
395 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
396 dmarc_status. It adds new control flags dmarc_disable_verify and
397 dmarc_enable_forensic.
399 22. Add expansion variable $authenticated_fail_id, which is the username
400 provided to the authentication method which failed. It is available
401 for use in subsequent ACL processing (typically quit or notquit ACLs).
403 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
406 24. New ${hexquote:..string..} expansion operator converts non-printable
407 characters in the string to \xNN form.
409 25. Experimental TPDA (Transport Post Delivery Action) function added.
410 Patch provided by Axel Rau.
412 26. Experimental Redis lookup added. Patch provided by Warren Baker.
418 1. New authenticator driver, "gsasl". Server-only (at present).
419 This is a SASL interface, licensed under GPL, which can be found at
420 http://www.gnu.org/software/gsasl/.
421 This system does not provide sources of data for authentication, so
422 careful use needs to be made of the conditions in Exim.
424 2. New authenticator driver, "heimdal_gssapi". Server-only.
425 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
426 is no longer honoured for setuid programs by Heimdal. Use the
427 "server_keytab" option to point to the keytab.
429 3. The "pkg-config" system can now be used when building Exim to reference
430 cflags and library information for lookups and authenticators, rather
431 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
432 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
433 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
435 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
436 find the headers and libraries for PCRE.
438 4. New expansion variable $tls_bits.
440 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
441 be joined together with ASCII NUL characters to construct the key to pass
442 into the DBM library. Can be used with gsasl to access sasldb2 files as
445 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
447 Avoid release 1.0.1a if you can. Note that the default value of
448 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
449 increased susceptibility to attack. This may still have interoperability
450 implications for very old clients (see version 4.31 change 37) but
451 administrators can choose to make the trade-off themselves and restore
452 compatibility at the cost of session security.
454 7. Use of the new expansion variable $tls_sni in the main configuration option
455 tls_certificate will cause Exim to re-expand the option, if the client
456 sends the TLS Server Name Indication extension, to permit choosing a
457 different certificate; tls_privatekey will also be re-expanded. You must
458 still set these options to expand to valid files when $tls_sni is not set.
460 The SMTP Transport has gained the option tls_sni, which will set a hostname
461 for outbound TLS sessions, and set $tls_sni too.
463 A new log_selector, +tls_sni, has been added, to log received SNI values
464 for Exim as a server.
466 8. The existing "accept_8bitmime" option now defaults to true. This means
467 that Exim is deliberately not strictly RFC compliant. We're following
468 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
469 Those who disagree, or know that they are talking to mail servers that,
470 even today, are not 8-bit clean, need to turn off this option.
472 9. Exim can now be started with -bw (with an optional timeout, given as
473 -bw<timespec>). With this, stdin at startup is a socket that is
474 already listening for connections. This has a more modern name of
475 "socket activation", but forcing the activated socket to fd 0. We're
476 interested in adding more support for modern variants.
478 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
479 for numbers indicates multiplication by 1024^3.
481 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
482 gnutls_require_mac & gnutls_require_protocols are no longer supported.
483 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
484 string, documentation for which is at:
485 http://www.gnutls.org/manual/html_node/Priority-Strings.html
487 SNI support has been added to Exim's GnuTLS integration too.
489 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
490 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
492 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
493 is now available. If the contents of the file are valid, then Exim will
494 send that back in response to a TLS status request; this is OCSP Stapling.
495 Exim will not maintain the contents of the file in any way: administrators
496 are responsible for ensuring that it is up-to-date.
498 See "experimental-spec.txt" for more details.
500 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
501 identically to TXT record lookups.
503 14. New expansion variable $tod_epoch_l for higher-precision time.
505 15. New global option tls_dh_max_bits, defaulting to current value of NSS
506 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
507 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
509 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
510 Option can now be a path or an identifier for a standard prime.
511 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
512 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
515 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
516 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
517 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
523 1. New options for the ratelimit ACL condition: /count= and /unique=.
524 The /noupdate option has been replaced by a /readonly option.
526 2. The SMTP transport's protocol option may now be set to "smtps", to
527 use SSL-on-connect outbound.
529 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
530 there is a problem talking to the AV scanner, or the AV scanner running.
532 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
533 and check if the search item is a member of the list. This does not
534 support named lists, but does subject the list part to string expansion.
536 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
537 built, Exim no longer performs string expansion on the second string of
538 the match_* expansion conditions: "match_address", "match_domain",
539 "match_ip" & "match_local_part". Named lists can still be used.
545 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
546 or off in the resolver library.
552 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
553 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
554 libraries. The following global options have been added in support of
555 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
556 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
558 2. The pipe transport now takes a boolean option, "freeze_signal", default
559 false. When true, if the external delivery command exits on a signal then
560 Exim will freeze the message in the queue, instead of generating a bounce.
562 3. Log filenames may now use %M as an escape, instead of %D (still available).
563 The %M pattern expands to yyyymm, providing month-level resolution.
565 4. The $message_linecount variable is now updated for the maildir_tag option,
566 in the same way as $message_size, to reflect the real number of lines,
567 including any header additions or removals from transport.
569 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
570 Exim now selects entries randomly, to better scale in a cluster setup.
576 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
577 the flaw permitted the Exim run-time user to cause root to append to
578 arbitrary files of the attacker's choosing, with the content based
579 on content supplied by the attacker.
581 2. Exim now supports loading some lookup types at run-time, using your
582 platform's dlopen() functionality. This has limited platform support
583 and the intention is not to support every variant, it's limited to
584 dlopen(). This permits the main Exim binary to not be linked against
585 all the libraries needed for all the lookup types.
591 NOTE: this version is not guaranteed backwards-compatible, please read the
592 items below carefully
594 1. A new main configuration option, "openssl_options", is available if Exim
595 is built with SSL support provided by OpenSSL. The option allows
596 administrators to specify OpenSSL options to be used on connections;
597 typically this is to set bug compatibility features which the OpenSSL
598 developers have not enabled by default. There may be security
599 consequences for certain options, so these should not be changed
602 2. A new pipe transport option, "permit_coredumps", may help with problem
603 diagnosis in some scenarios. Note that Exim is typically installed as
604 a setuid binary, which on most OSes will inhibit coredumps by default,
605 so that safety mechanism would have to be overridden for this option to
606 be able to take effect.
608 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
609 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
610 Note that this switches Exim to use a new API ("INSTREAM") and a future
611 release of ClamAV will remove support for the old API ("STREAM").
613 The av_scanner option, when set to "clamd", now takes an optional third
614 part, "local", which causes Exim to pass a filename to ClamAV instead of
615 the file content. This is the same behaviour as when clamd is pointed at
616 a Unix-domain socket. For example:
618 av_scanner = clamd:192.0.2.3 1234:local
620 ClamAV's ExtendedDetectionInfo response format is now handled.
622 4. There is now a -bmalware option, restricted to admin users. This option
623 takes one parameter, a filename, and scans that file with Exim's
624 malware-scanning framework. This is intended purely as a debugging aid
625 to ensure that Exim's scanning is working, not to replace other tools.
626 Note that the ACL framework is not invoked, so if av_scanner references
627 ACL variables without a fallback then this will fail.
629 5. There is a new expansion operator, "reverse_ip", which will reverse IP
630 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
632 ${reverse_ip:192.0.2.4}
634 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
635 -> 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
637 6. There is a new ACL control called "debug", to enable debug logging.
638 This allows selective logging of certain incoming transactions within
639 production environments, with some care. It takes two options, "tag"
640 and "opts"; "tag" is included in the filename of the log and "opts"
641 is used as per the -d<options> command-line option. Examples, which
642 don't all make sense in all contexts:
645 control = debug/tag=.$sender_host_address
646 control = debug/opts=+expand+acl
647 control = debug/tag=.$message_exim_id/opts=+expand
649 7. It has always been implicit in the design and the documentation that
650 "the Exim user" is not root. src/EDITME said that using root was
651 "very strongly discouraged". This is not enough to keep people from
652 shooting themselves in the foot in days when many don't configure Exim
653 themselves but via package build managers. The security consequences of
654 running various bits of network code are severe if there should be bugs in
655 them. As such, the Exim user may no longer be root. If configured
656 statically, Exim will refuse to build. If configured as ref:user then Exim
657 will exit shortly after start-up. If you must shoot yourself in the foot,
658 then henceforth you will have to maintain your own local patches to strip
661 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
662 condition logic to determine truth/failure and will fail to expand many
663 strings, bool_lax{} uses the router condition logic, where most strings
665 Note: bool{00} is false, bool_lax{00} is true.
667 9. Routers now support multiple "condition" tests.
669 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
670 Setting this allows an admin to define which entry in the tcpwrappers
671 config file will be used to control access to the daemon. This option
672 is only available when Exim is built with USE_TCP_WRAPPERS. The
673 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
676 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
677 the Exim run-time user, instead of root.
679 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
680 is forced on. This is mitigated by the new build option
681 TRUSTED_CONFIG_LIST which defines a list of configuration files which
682 are trusted; one per line. If a config file is owned by root and matches
683 a pathname in the list, then it may be invoked by the Exim build-time
684 user without Exim relinquishing root privileges.
686 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
687 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
688 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
689 include the main config. As a transition mechanism, we are temporarily
690 providing a work-around: the new build option WHITELIST_D_MACROS provides
691 a colon-separated list of macro names which may be overridden by the Exim
692 run-time user. The values of these macros are constrained to the regex
693 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
699 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
700 writable, the other to locking of MBX folders (not mbox).
702 2. MySQL stored procedures are now supported.
704 3. The dkim_domain transport option is now a list, not a single string, and
705 messages will be signed for each element in the list (discarding
708 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
709 in the presence of multiple character strings within the RR. Prior to 4.70,
710 only the first string would be returned. The dnsdb lookup now, by default,
711 preserves the pre-4.70 semantics, but also now takes an extended output
712 separator specification. The separator can be followed by a semicolon, to
713 concatenate the individual text strings together with no join character,
714 or by a comma and a second separator character, in which case the text
715 strings within a TXT record are joined on that second character.
716 Administrators are reminded that DNS provides no ordering guarantees
717 between multiple records in an RRset. For example:
719 foo.example. IN TXT "a" "b" "c"
720 foo.example. IN TXT "d" "e" "f"
722 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
723 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
724 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
730 1. Native DKIM support without an external library.
731 (Note that if no action to prevent it is taken, a straight upgrade will
732 result in DKIM verification of all signed incoming emails. See spec
733 for details on conditionally disabling)
735 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
737 3. There is now a bool{} expansion condition which maps certain strings to
738 true/false condition values (most likely of use in conjunction with the
739 and{} expansion operator).
741 4. The $spam_score, $spam_bar and $spam_report variables are now available
744 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
745 options, provided that Exim is invoked by an admin_user.
747 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
748 which increases compatibility with older clients at the cost of decreased
749 security. Don't set this unless you need to support such clients.
751 7. There is a new expansion operator, ${randint:...} which will produce a
752 "random" number less than the supplied integer. This randomness is
753 not guaranteed to be cryptographically strong, but depending upon how
754 Exim was built may be better than the most naive schemes.
756 8. Exim now explicitly ensures that SHA256 is available when linked against
759 9. The transport_filter_timeout option now applies to SMTP transports too.
765 1. Preliminary DKIM support in Experimental.
771 1. The body_linecount and body_zerocount C variables are now exported in the
774 2. When a dnslists lookup succeeds, the key that was looked up is now placed
775 in $dnslist_matched. When the key is an IP address, it is not reversed in
776 this variable (though it is, of course, in the actual lookup). In simple
779 deny dnslists = spamhaus.example
781 the key is also available in another variable (in this case,
782 $sender_host_address). In more complicated cases, however, this is not
783 true. For example, using a data lookup might generate a dnslists lookup
786 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
788 If this condition succeeds, the value in $dnslist_matched might be
789 192.168.6.7 (for example).
791 3. Authenticators now have a client_condition option. When Exim is running as
792 a client, it skips an authenticator whose client_condition expansion yields
793 "0", "no", or "false". This can be used, for example, to skip plain text
794 authenticators when the connection is not encrypted by a setting such as:
796 client_condition = ${if !eq{$tls_cipher}{}}
798 Note that the 4.67 documentation states that $tls_cipher contains the
799 cipher used for incoming messages. In fact, during SMTP delivery, it
800 contains the cipher used for the delivery. The same is true for
803 4. There is now a -Mvc <message-id> option, which outputs a copy of the
804 message to the standard output, in RFC 2822 format. The option can be used
805 only by an admin user.
807 5. There is now a /noupdate option for the ratelimit ACL condition. It
808 computes the rate and checks the limit as normal, but it does not update
809 the saved data. This means that, in relevant ACLs, it is possible to lookup
810 the existence of a specified (or auto-generated) ratelimit key without
811 incrementing the ratelimit counter for that key.
813 In order for this to be useful, another ACL entry must set the rate
814 for the same key somewhere (otherwise it will always be zero).
819 # Read the rate; if it doesn't exist or is below the maximum
821 deny ratelimit = 100 / 5m / strict / noupdate
822 log_message = RATE: $sender_rate / $sender_rate_period \
823 (max $sender_rate_limit)
825 [... some other logic and tests...]
827 warn ratelimit = 100 / 5m / strict / per_cmd
828 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
829 (max $sender_rate_limit)
830 condition = ${if le{$sender_rate}{$sender_rate_limit}}
834 6. The variable $max_received_linelength contains the number of bytes in the
835 longest line that was received as part of the message, not counting the
836 line termination character(s).
838 7. Host lists can now include +ignore_defer and +include_defer, analagous to
839 +ignore_unknown and +include_unknown. These options should be used with
840 care, probably only in non-critical host lists such as whitelists.
842 8. There's a new option called queue_only_load_latch, which defaults true.
843 If set false when queue_only_load is greater than zero, Exim re-evaluates
844 the load for each incoming message in an SMTP session. Otherwise, once one
845 message is queued, the remainder are also.
847 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
848 cases when an SMTP session ends without sending QUIT. However, when Exim
849 itself is is bad trouble, such as being unable to write to its log files,
850 this ACL is not run, because it might try to do things (such as write to
851 log files) that make the situation even worse.
853 Like the QUIT ACL, this new ACL is provided to make it possible to gather
854 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
855 modifier is forbidden in this ACL.
857 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
858 to a string that indicates the reason for the termination of the SMTP
859 connection. The possible values are:
861 acl-drop Another ACL issued a "drop" command
862 bad-commands Too many unknown or non-mail commands
863 command-timeout Timeout while reading SMTP commands
864 connection-lost The SMTP connection has been lost
865 data-timeout Timeout while reading message data
866 local-scan-error The local_scan() function crashed
867 local-scan-timeout The local_scan() function timed out
868 signal-exit SIGTERM or SIGINT
869 synchronization-error SMTP synchronization error
870 tls-failed TLS failed to start
872 In most cases when an SMTP connection is closed without having received
873 QUIT, Exim sends an SMTP response message before actually closing the
874 connection. With the exception of acl-drop, the default message can be
875 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
876 "drop" verb in another ACL, it is the message from the other ACL that is
879 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
880 servers with individual queries. This is done by starting the query with
881 "servers=x:y:z;", where each item in the list may take one of two forms:
883 (1) If it is just a host name, the appropriate global option (mysql_servers
884 or pgsql_servers) is searched for a host of the same name, and the
885 remaining parameters (database, user, password) are taken from there.
887 (2) If it contains any slashes, it is taken as a complete parameter set.
889 The list of servers is used in exactly the same was as the global list.
890 Once a connection to a server has happened and a query has been
891 successfully executed, processing of the lookup ceases.
893 This feature is intended for use in master/slave situations where updates
894 are occurring, and one wants to update a master rather than a slave. If the
895 masters are in the list for reading, you might have:
897 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
899 In an updating lookup, you could then write
901 ${lookup mysql{servers=master; UPDATE ...}
903 If, on the other hand, the master is not to be used for reading lookups:
905 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
907 you can still update the master by
909 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
911 11. The message_body_newlines option (default FALSE, for backwards
912 compatibility) can be used to control whether newlines are present in
913 $message_body and $message_body_end. If it is FALSE, they are replaced by
920 1. There is a new log selector called smtp_no_mail, which is not included in
921 the default setting. When it is set, a line is written to the main log
922 whenever an accepted SMTP connection terminates without having issued a
925 2. When an item in a dnslists list is followed by = and & and a list of IP
926 addresses, the behaviour was not clear when the lookup returned more than
927 one IP address. This has been solved by the addition of == and =& for "all"
928 rather than the default "any" matching.
930 3. Up till now, the only control over which cipher suites GnuTLS uses has been
931 for the cipher algorithms. New options have been added to allow some of the
932 other parameters to be varied.
934 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
935 set, Exim compiles a runtime option called disable_fsync.
937 5. There is a new variable called $smtp_count_at_connection_start.
939 6. There's a new control called no_pipelining.
941 7. There are two new variables called $sending_ip_address and $sending_port.
942 These are set whenever an SMTP connection to another host has been set up.
944 8. The expansion of the helo_data option in the smtp transport now happens
945 after the connection to the server has been made.
947 9. There is a new expansion operator ${rfc2047d: that decodes strings that
948 are encoded as per RFC 2047.
950 10. There is a new log selector called "pid", which causes the current process
951 id to be added to every log line, in square brackets, immediately after the
954 11. Exim has been modified so that it flushes SMTP output before implementing
955 a delay in an ACL. It also flushes the output before performing a callout,
956 as this can take a substantial time. These behaviours can be disabled by
957 obeying control = no_delay_flush or control = no_callout_flush,
958 respectively, at some earlier stage of the connection.
960 12. There are two new expansion conditions that iterate over a list. They are
961 called forany and forall.
963 13. There's a new global option called dsn_from that can be used to vary the
964 contents of From: lines in bounces and other automatically generated
965 messages ("delivery status notifications" - hence the name of the option).
967 14. The smtp transport has a new option called hosts_avoid_pipelining.
969 15. By default, exigrep does case-insensitive matches. There is now a -I option
970 that makes it case-sensitive.
972 16. A number of new features ("addresses", "map", "filter", and "reduce") have
973 been added to string expansions to make it easier to process lists of
974 items, typically addresses.
976 17. There's a new ACL modifier called "continue". It does nothing of itself,
977 and processing of the ACL always continues with the next condition or
978 modifier. It is provided so that the side effects of expanding its argument
981 18. It is now possible to use newline and other control characters (those with
982 values less than 32, plus DEL) as separators in lists.
984 19. The exigrep utility now has a -v option, which inverts the matching
987 20. The host_find_failed option in the manualroute router can now be set to
994 No new features were added to 4.66.
1000 No new features were added to 4.65.
1006 1. ACL variables can now be given arbitrary names, as long as they start with
1007 "acl_c" or "acl_m" (for connection variables and message variables), are at
1008 least six characters long, with the sixth character being either a digit or
1011 2. There is a new ACL modifier called log_reject_target. It makes it possible
1012 to specify which logs are used for messages about ACL rejections.
1014 3. There is a new authenticator called "dovecot". This is an interface to the
1015 authentication facility of the Dovecot POP/IMAP server, which can support a
1016 number of authentication methods.
1018 4. The variable $message_headers_raw provides a concatenation of all the
1019 messages's headers without any decoding. This is in contrast to
1020 $message_headers, which does RFC2047 decoding on the header contents.
1022 5. In a DNS black list, if two domain names, comma-separated, are given, the
1023 second is used first to do an initial check, making use of any IP value
1024 restrictions that are set. If there is a match, the first domain is used,
1025 without any IP value restrictions, to get the TXT record.
1027 6. All authenticators now have a server_condition option.
1029 7. There is a new command-line option called -Mset. It is useful only in
1030 conjunction with -be (that is, when testing string expansions). It must be
1031 followed by a message id; Exim loads the given message from its spool
1032 before doing the expansions.
1034 8. Another similar new command-line option is called -bem. It operates like
1035 -be except that it must be followed by the name of a file that contains a
1038 9. When an address is delayed because of a 4xx response to a RCPT command, it
1039 is now the combination of sender and recipient that is delayed in
1040 subsequent queue runs until its retry time is reached.
1042 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1043 shift, have been added to the eval: and eval10: expansion items.
1045 11. The variables $interface_address and $interface_port have been renamed
1046 as $received_ip_address and $received_port, to make it clear that they
1047 relate to message reception rather than delivery. (The old names remain
1048 available for compatibility.)
1050 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1051 to vary the message that is sent when an SMTP command is accepted.
1057 1. There is a new Boolean option called filter_prepend_home for the redirect
1060 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1061 start of receiving a non-SMTP message, before any of the message has been
1064 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1065 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1066 start of the message for an SMTP error code.
1068 4. There is a new parameter for LDAP lookups called "referrals", which takes
1069 one of the settings "follow" (the default) or "nofollow".
1071 5. Version 20070721.2 of exipick now included, offering these new options:
1073 After all other sorting options have bee processed, reverse order
1074 before displaying messages (-R is synonym).
1076 Randomize order of matching messages before displaying.
1078 Instead of displaying the matching messages, display the sum
1080 --sort <variable>[,<variable>...]
1081 Before displaying matching messages, sort the messages according to
1082 each messages value for each variable.
1084 Negate the value for every test (returns inverse output from the
1085 same criteria without --not).
1091 1. The ${readsocket expansion item now supports Internet domain sockets as well
1092 as Unix domain sockets. If the first argument begins "inet:", it must be of
1093 the form "inet:host:port". The port is mandatory; it may be a number or the
1094 name of a TCP port in /etc/services. The host may be a name, or it may be an
1095 IP address. An ip address may optionally be enclosed in square brackets.
1096 This is best for IPv6 addresses. For example:
1098 ${readsocket{inet:[::1]:1234}{<request data>}...
1100 Only a single host name may be given, but if looking it up yield more than
1101 one IP address, they are each tried in turn until a connection is made. Once
1102 a connection has been made, the behaviour is as for ${readsocket with a Unix
1105 2. If a redirect router sets up file or pipe deliveries for more than one
1106 incoming address, and the relevant transport has batch_max set greater than
1107 one, a batch delivery now occurs.
1109 3. The appendfile transport has a new option called maildirfolder_create_regex.
1110 Its value is a regular expression. For a maildir delivery, this is matched
1111 against the maildir directory; if it matches, Exim ensures that a
1112 maildirfolder file is created alongside the new, cur, and tmp directories.
1118 The documentation is up-to-date for the 4.61 release. Major new features since
1119 the 4.60 release are:
1121 . An option called disable_ipv6, to disable the use of IPv6 completely.
1123 . An increase in the number of ACL variables to 20 of each type.
1125 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1126 $2, $3, (though those are still set) because the numeric variables get used
1127 for other things in complicated expansions.
1129 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1131 . It is possible to use setclassresources() on some BSD OS to control the
1132 resources used in pipe deliveries.
1134 . A new ACL modifier called add_header, which can be used with any verb.
1136 . More errors are detectable in retry rules.
1138 There are a number of other additions too.
1144 The documentation is up-to-date for the 4.60 release. Major new features since
1145 the 4.50 release are:
1147 . Support for SQLite.
1149 . Support for IGNOREQUOTA in LMTP.
1151 . Extensions to the "submission mode" features.
1153 . Support for Client SMTP Authorization (CSA).
1155 . Support for ratelimiting hosts and users.
1157 . New expansion items to help with the BATV "prvs" scheme.
1159 . A "match_ip" condition, that matches an IP address against a list.
1161 There are many more minor changes.
git://git.exim.org / exim.git / blob