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. An "external" authenticator, per RFC 4422 Appendix A.
14 2. A JSON lookup type, and JSON variants of the forall/any expansion conditions.
16 3. Variables $tls_in_cipher_std, $tls_out_cipher_std giving the RFC names
19 4. Log_selectors "msg_id" (on by default) and "msg_id_created".
21 5. A case_insensitive option for verify=not_blind.
23 6. EXPERIMENTAL_TLS_RESUME optional build feature. See the experimental.spec
26 7. A main option exim_version to override the version Exim
27 reports in verious places ($exim_version, $version_number).
29 8. Expansion operator ${sha2_N:} for N=256, 384, 512.
31 9. Router variables, $r_... settable from router options and usable in routers
34 10. The spf lookup now supports IPv6.
36 11. Main options for DKIM verify to filter hash and key types.
38 12. With TLS1.3, support for full-chain OCSP stapling.
40 13. Dual-certificate stacks on servers now support OCSP stapling, under OpenSSL.
42 14: An smtp:ehlo transport event, for observability of the remote offered features.
44 15: Support under OpenSSL for writing NSS-style key files for packet-capture
45 decode. The environment variable SSLKEYLOGFILE is used; if an absolute path
46 it must indicate a file under the spool directory; if relative the the spool
47 directory is prepended. Works on the server side only. Support under
48 GnuTLS was already there, being done purely by the library (server side
49 only, and exim must be run as root).
51 16: Command-line option to move messages from one named queue to another.
57 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
58 list when there are multiple headers having a given name. This matters
59 when individual headers are wrapped onto multiple lines; with previous
60 facilities hard to parse.
62 2. The ${readsocket } expansion item now takes a "tls" option, doing the
65 3. EXPERIMENTAL_REQUIRETLS and EXPERIMENTAL_PIPE_CONNECT optional build
66 features. See the experimental.spec file.
68 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
70 5. A "pipelining" log_selector.
72 6. Builtin macros for supported log_selector and openssl_options values.
74 7. JSON variants of the ${extract } expansion item.
76 8. A "noutf8" debug option, for disabling the UTF-8 characters in debug output.
78 9. TCP Fast Open support on MacOS.
83 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
84 version 3.5.6 or later.
86 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
87 OpenSSL versions are moved to mainline support from Experimental.
88 New SMTP transport option "dane_require_tls_ciphers".
90 3. Feature macros for the compiled-in set of malware scanner interfaces.
92 4. SPF support is promoted from Experimental to mainline status. The template
93 src/EDITME makefile does not enable its inclusion.
95 5. Logging control for DKIM verification. The existing DKIM log line is
96 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
97 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
98 a "dkim" log_selector.
100 6. Receive duration on <= lines, under a new log_selector "receive_time".
102 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
103 routing rules in the manualroute router.
105 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
106 under OpenSSL version 1.1.1 or later.
108 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
109 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
111 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
114 11. "exim -bP macro <name>" returns caller-usable status.
116 12. Expansion item ${authresults {<machine>}} for creating an
117 Authentication-Results: header.
119 13. EXPERIMENTAL_ARC. See the experimental.spec file.
120 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
122 14: A dane:fail event, intended to facilitate reporting.
124 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
125 contain all the servers in the cluster, all of which must be reachable from
126 the running exim instance. If the cluster has master/slave replication, the
127 list must contain all the master and slave servers.
129 16. Add an option to the Avast scanner interface: "pass_unscanned". This
130 allows to treat unscanned files as clean. Files may be unscanned for
131 several reasons: decompression bombs, broken archives.
137 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
138 wildcards will be expanded, values are collapsed.
140 2. The ${readsocket } expansion now takes an option to not shutdown the
141 connection after sending the query string. The default remains to do so.
143 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
144 deliveries on a single TCP connection can maintain a TLS connection
145 open. By default disabled for all hosts, doing so saves the cost of
146 making new TLS sessions, at the cost of having to proxy the data via
147 another process. Logging is also affected.
149 4. A malware connection type for the FPSCAND protocol.
151 5. An option for recipient verify callouts to hold the connection open for
152 further recipients and for delivery.
154 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
157 7. Optionally, an alternate format for spool data-files which matches the
158 wire format - meaning more efficient reception and transmission (at the
159 cost of difficulty with standard Unix tools). Only used for messages
160 received using the ESMTP CHUNKING option, and when a new main-section
161 option "spool_wireformat" (false by default) is set.
163 8. New main configuration option "commandline_checks_require_admin" to
164 restrict who can use various introspection options.
166 9. New option modifier "no_check" for quota and quota_filecount
167 appendfile transport.
169 10. Variable $smtp_command_history returning a comma-sep list of recent
172 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
173 log elements QT, DT and D, and timstamps in debug output.
175 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
176 while still in SYN_RECV state; as a client logs when the connection
177 is opened with a TFO cookie.
179 13. DKIM support for multiple signing, by domain and/or key-selector.
180 DKIM support for multiple hashes, and for alternate-identity tags.
181 Builtin macro with default list of signed headers.
182 Better syntax for specifying oversigning.
183 The DKIM ACL can override verification status, and status is visible in
186 14. Exipick understands -C|--config for an alternative Exim
189 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
190 for ${readsocket } expansions, and for ClamAV.
192 16. The "-be" expansion test mode now supports macros. Macros are expanded
193 in test lines, and new macros can be defined.
195 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
201 1. Allow relative config file names for ".include"
203 2. A main-section config option "debug_store" to control the checks on
204 variable locations during store-reset. Normally false but can be enabled
205 when a memory corruption issue is suspected on a production system.
211 1. The new perl_taintmode option allows to run the embedded perl
212 interpreter in taint mode.
214 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
216 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
219 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
220 N can be 224, 256 (default), 384, 512.
221 With GnuTLS 3.5.0 or later, only.
223 5. Facility for named queues: A command-line argument can specify
224 the queue name for a queue operation, and an ACL modifier can set
225 the queue to be used for a message. A $queue_name variable gives
228 6. New expansion operators base32/base32d.
230 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
231 performance increase and network load decrease. Main config option
232 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
235 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
237 9. Expansion operator escape8bit, like escape but not touching newline etc..
239 10. Feature macros, generated from compile options. All start with "_HAVE_"
240 and go on with some roughly recognisable name. Driver macros, for
241 router, transport and authentication drivers; names starting with "_DRIVER_".
242 Option macros, for each configuration-file option; all start with "_OPT_".
243 Use the "-bP macros" command-line option to see what is present.
245 11. Integer values for options can take a "G" multiplier.
247 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
248 returns from the target back to the initiator, rather than spooling the
251 13. New built-in constants available for tls_dhparam and default changed.
253 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
254 out copies of the message spool files for use by 3rd-party scanners.
256 15. A new option on the smtp transport, hosts_try_fastopen. If the system
257 supports it (on Linux it must be enabled in the kernel by the sysadmin)
258 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
259 but it permits a peer that also supports the facility to send its SMTP
260 banner immediately after the SYN,ACK segment rather then waiting for
261 another ACK - so saving up to one roundtrip time. Because it requires
262 previous communication with the peer (we save a cookie from it) this
263 will only become active on frequently-contacted destinations.
265 16. A new syslog_pid option to suppress PID duplication in syslog lines.
271 1. The ACL conditions regex and mime_regex now capture substrings
272 into numeric variables $regex1 to 9, like the "match" expansion condition.
274 2. New $callout_address variable records the address used for a spam=,
275 malware= or verify= callout.
277 3. Transports now take a "max_parallel" option, to limit concurrency.
279 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
280 The latter expands to a 8-element colon-sep set of hex digits including
281 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
282 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
283 The former operator strips leading zeroes and collapses the longest
284 set of 0-groups to a double-colon.
286 5. New "-bP config" support, to dump the effective configuration.
288 6. New $dkim_key_length variable.
290 7. New base64d and base64 expansion items (the existing str2b64 being a
291 synonym of the latter). Add support in base64 for certificates.
293 8. New main configuration option "bounce_return_linesize_limit" to
294 avoid oversize bodies in bounces. The default value matches RFC
297 9. New $initial_cwd expansion variable.
303 1. Support for using the system standard CA bundle.
305 2. New expansion items $config_file, $config_dir, containing the file
306 and directory name of the main configuration file. Also $exim_version.
308 3. New "malware=" support for Avast.
310 4. New "spam=" variant option for Rspamd.
312 5. Assorted options on malware= and spam= scanners.
314 6. A command-line option to write a comment into the logfile.
316 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
317 be configured to make connections via socks5 proxies.
319 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
320 the transmission of UTF-8 envelope addresses.
322 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
323 used encoding of Maildir folder names.
325 10. A logging option for slow DNS lookups.
327 11. New ${env {<variable>}} expansion.
329 12. A non-SMTP authenticator using information from TLS client certificates.
331 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
332 Patch originally by Wolfgang Breyha.
334 14. Main option "dns_trust_aa" for trusting your local nameserver at the
335 same level as DNSSEC.
341 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
342 DANE SMTP draft to assess a secure chain of trust of the certificate
343 used to establish the TLS connection based on a TLSA record in the
344 domain of the sender.
346 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
347 and several new events have been created. The reason is because it has
348 been expanded beyond just firing events during the transport phase. Any
349 existing TPDA transport options will have to be rewritten to use a new
350 $event_name expansion variable in a condition. Refer to the
351 experimental-spec.txt for details and examples.
353 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
354 server certs used for TLS match the result of the MX lookup. It does
355 not use the same mechanism as DANE.
365 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
366 configured to expect an initial header from a proxy that will make the
367 actual external source IP:host be used in exim instead of the IP of the
368 proxy that is connecting to it.
370 2. New verify option header_names_ascii, which will check to make sure
371 there are no non-ASCII characters in header names. Exim itself handles
372 those non-ASCII characters, but downstream apps may not, so Exim can
373 detect and reject if those characters are present.
375 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
376 codepoints with valid ones.
378 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
379 command line and matching a regex against the return data for trigger
380 and a second regex to extract malware_name. The mail spoolfile name can
381 be included in the command line.
383 5. The smtp transport now supports options "tls_verify_hosts" and
384 "tls_try_verify_hosts". If either is set the certificate verification
385 is split from the encryption operation. The default remains that a failed
386 verification cancels the encryption.
388 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
389 lookup can now set a list of servers to use that is different from the
392 7. New command-line option -C for exiqgrep to specify alternate exim.conf
393 file when searching the queue.
395 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
397 9. Support for DNSSEC on outbound connections.
399 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
400 "certextract" to extract fields from them. Hash operators md5 and sha1
401 work over them for generating fingerprints, and a new sha256 operator
404 11. PRDR is now supported dy default.
406 12. OCSP stapling is now supported by default.
408 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
409 Delivery Status Notification messages in MIME format, and negotiate
410 DSN features per RFC 3461.
416 1. New command-line option -bI:sieve will list all supported sieve extensions
417 of this Exim build on standard output, one per line.
418 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
419 query this to establish the correct list to include in the protocol's
420 SIEVE capability line.
422 2. If the -n option is combined with the -bP option, then the name of an
423 emitted option is not output, only the value (if visible to you).
424 For instance, "exim -n -bP pid_file_path" should just emit a pathname
425 followed by a newline, and no other text.
427 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
428 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
429 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
430 acceptable for security. (Option accepted but ignored if using OpenSSL).
431 Defaults to 1024, the old value. May be lowered only to 512, or raised as
432 far as you like. Raising this may hinder TLS interoperability with other
433 sites and is not currently recommended. Lowering this will permit you to
434 establish a TLS session which is not as secure as you might like.
436 Unless you really know what you are doing, leave it alone.
438 4. If not built with DISABLE_DNSSEC, Exim now has the main option
439 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
440 to send the DO flag to your recursive resolver. If you have a recursive
441 resolver, which can set the Authenticated Data (AD) flag in results, Exim
442 can now detect this. Exim does not perform validation itself, instead
443 relying upon a trusted path to the resolver.
445 Current status: work-in-progress; $sender_host_dnssec variable added.
447 5. DSCP support for outbound connections: on a transport using the smtp driver,
448 set "dscp = ef", for instance, to cause the connections to have the relevant
449 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
451 Similarly for inbound connections, there is a new control modifier, dscp,
452 so "warn control = dscp/ef" in the connect ACL, or after authentication.
454 Supported values depend upon system libraries. "exim -bI:dscp" to list the
455 ones Exim knows of. You can also set a raw number 0..0x3F.
457 6. The -G command-line flag is no longer ignored; it is now equivalent to an
458 ACL setting "control = suppress_local_fixups". The -L command-line flag
459 is now accepted and forces use of syslog, with the provided tag as the
460 process name. A few other flags used by Sendmail are now accepted and
463 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
464 ACL modifier; works for single-recipient mails which are received on and
465 deliverable via SMTP. Using the connection made for a recipient verify,
466 if requested before the verify, or a new one made for the purpose while
467 the inbound connection is still active. The bulk of the mail item is copied
468 direct from the inbound socket to the outbound (as well as the spool file).
469 When the source notifies the end of data, the data acceptance by the destination
470 is negotiated before the acceptance is sent to the source. If the destination
471 does not accept the mail item, for example due to content-scanning, the item
472 is not accepted from the source and therefore there is no need to generate
473 a bounce mail. This is of benefit when providing a secondary-MX service.
474 The downside is that delays are under the control of the ultimate destination
477 The Received-by: header on items delivered by cutthrough is generated
478 early in reception rather than at the end; this will affect any timestamp
479 included. The log line showing delivery is recorded before that showing
480 reception; it uses a new ">>" tag instead of "=>".
482 To support the feature, verify-callout connections can now use ESMTP and TLS.
483 The usual smtp transport options are honoured, plus a (new, default everything)
484 hosts_verify_avoid_tls.
486 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
487 for specific access to the information for each connection. The old names
488 are present for now but deprecated.
490 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
492 8. New expansion operators ${listnamed:name} to get the content of a named list
493 and ${listcount:string} to count the items in a list.
495 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
496 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
497 modules. For some situations this is desirable, but we expect admin in
498 those situations to know they want the feature. More commonly, it means
499 that GUI user modules get loaded and are broken by the setuid Exim being
500 unable to access files specified in environment variables and passed
501 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
502 unless this new option is set.
504 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
505 so have also added a build option which can be used to build Exim with GnuTLS
506 but without trying to use any kind of PKCS11 support. Uncomment this in the
509 AVOID_GNUTLS_PKCS11=yes
511 10. The "acl = name" condition on an ACL now supports optional arguments.
512 New expansion item "${acl {name}{arg}...}" and expansion condition
513 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
514 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
515 Variable $acl_narg contains the number of arguments. If the ACL sets
516 a "message =" value this becomes the result of the expansion item,
517 or the value of $value for the expansion condition. If the ACL returns
518 accept the expansion condition is true; if reject, false. A defer
519 return results in a forced fail.
521 11. Routers and transports can now have multiple headers_add and headers_remove
522 option lines. The concatenated list is used.
524 12. New ACL modifier "remove_header" can remove headers before message gets
525 handled by routers/transports.
527 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
528 "aaaa" and "a" lookups is done and the full set of results returned.
530 14. New expansion variable $headers_added with content from ACL add_header
531 modifier (but not yet added to message).
533 15. New 8bitmime status logging option for received messages. Log field "M8S".
535 16. New authenticated_sender logging option, adding to log field "A".
537 17. New expansion variables $router_name and $transport_name. Useful
538 particularly for debug_print as -bt command-line option does not
539 require privilege whereas -d does.
541 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
542 proposed extension to SMTP from Eric Hall.
544 19. The pipe transport has gained the force_command option, to allow
545 decorating commands from user .forward pipe aliases with prefix
546 wrappers, for instance.
548 20. Callout connections can now AUTH; the same controls as normal delivery
551 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
552 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
553 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
554 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
555 dmarc_status. It adds new control flags dmarc_disable_verify and
556 dmarc_enable_forensic. The default for the dmarc_tld_file option is
557 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
559 22. Add expansion variable $authenticated_fail_id, which is the username
560 provided to the authentication method which failed. It is available
561 for use in subsequent ACL processing (typically quit or notquit ACLs).
563 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
566 24. New ${hexquote:..string..} expansion operator converts non-printable
567 characters in the string to \xNN form.
569 25. Experimental TPDA (Transport Post Delivery Action) function added.
570 Patch provided by Axel Rau.
572 26. Experimental Redis lookup added. Patch provided by Warren Baker.
578 1. New authenticator driver, "gsasl". Server-only (at present).
579 This is a SASL interface, licensed under GPL, which can be found at
580 http://www.gnu.org/software/gsasl/.
581 This system does not provide sources of data for authentication, so
582 careful use needs to be made of the conditions in Exim.
584 2. New authenticator driver, "heimdal_gssapi". Server-only.
585 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
586 is no longer honoured for setuid programs by Heimdal. Use the
587 "server_keytab" option to point to the keytab.
589 3. The "pkg-config" system can now be used when building Exim to reference
590 cflags and library information for lookups and authenticators, rather
591 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
592 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
593 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
595 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
596 find the headers and libraries for PCRE.
598 4. New expansion variable $tls_bits.
600 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
601 be joined together with ASCII NUL characters to construct the key to pass
602 into the DBM library. Can be used with gsasl to access sasldb2 files as
605 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
607 Avoid release 1.0.1a if you can. Note that the default value of
608 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
609 increased susceptibility to attack. This may still have interoperability
610 implications for very old clients (see version 4.31 change 37) but
611 administrators can choose to make the trade-off themselves and restore
612 compatibility at the cost of session security.
614 7. Use of the new expansion variable $tls_sni in the main configuration option
615 tls_certificate will cause Exim to re-expand the option, if the client
616 sends the TLS Server Name Indication extension, to permit choosing a
617 different certificate; tls_privatekey will also be re-expanded. You must
618 still set these options to expand to valid files when $tls_sni is not set.
620 The SMTP Transport has gained the option tls_sni, which will set a hostname
621 for outbound TLS sessions, and set $tls_sni too.
623 A new log_selector, +tls_sni, has been added, to log received SNI values
624 for Exim as a server.
626 8. The existing "accept_8bitmime" option now defaults to true. This means
627 that Exim is deliberately not strictly RFC compliant. We're following
628 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
629 Those who disagree, or know that they are talking to mail servers that,
630 even today, are not 8-bit clean, need to turn off this option.
632 9. Exim can now be started with -bw (with an optional timeout, given as
633 -bw<timespec>). With this, stdin at startup is a socket that is
634 already listening for connections. This has a more modern name of
635 "socket activation", but forcing the activated socket to fd 0. We're
636 interested in adding more support for modern variants.
638 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
639 for numbers indicates multiplication by 1024^3.
641 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
642 gnutls_require_mac & gnutls_require_protocols are no longer supported.
643 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
644 string, documentation for which is at:
645 http://www.gnutls.org/manual/html_node/Priority-Strings.html
647 SNI support has been added to Exim's GnuTLS integration too.
649 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
650 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
652 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
653 is now available. If the contents of the file are valid, then Exim will
654 send that back in response to a TLS status request; this is OCSP Stapling.
655 Exim will not maintain the contents of the file in any way: administrators
656 are responsible for ensuring that it is up-to-date.
658 See "experimental-spec.txt" for more details.
660 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
661 identically to TXT record lookups.
663 14. New expansion variable $tod_epoch_l for higher-precision time.
665 15. New global option tls_dh_max_bits, defaulting to current value of NSS
666 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
667 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
669 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
670 Option can now be a path or an identifier for a standard prime.
671 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
672 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
675 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
676 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
677 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
683 1. New options for the ratelimit ACL condition: /count= and /unique=.
684 The /noupdate option has been replaced by a /readonly option.
686 2. The SMTP transport's protocol option may now be set to "smtps", to
687 use SSL-on-connect outbound.
689 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
690 there is a problem talking to the AV scanner, or the AV scanner running.
692 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
693 and check if the search item is a member of the list. This does not
694 support named lists, but does subject the list part to string expansion.
696 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
697 built, Exim no longer performs string expansion on the second string of
698 the match_* expansion conditions: "match_address", "match_domain",
699 "match_ip" & "match_local_part". Named lists can still be used.
705 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
706 or off in the resolver library.
712 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
713 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
714 libraries. The following global options have been added in support of
715 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
716 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
718 2. The pipe transport now takes a boolean option, "freeze_signal", default
719 false. When true, if the external delivery command exits on a signal then
720 Exim will freeze the message in the queue, instead of generating a bounce.
722 3. Log filenames may now use %M as an escape, instead of %D (still available).
723 The %M pattern expands to yyyymm, providing month-level resolution.
725 4. The $message_linecount variable is now updated for the maildir_tag option,
726 in the same way as $message_size, to reflect the real number of lines,
727 including any header additions or removals from transport.
729 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
730 Exim now selects entries randomly, to better scale in a cluster setup.
736 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
737 the flaw permitted the Exim run-time user to cause root to append to
738 arbitrary files of the attacker's choosing, with the content based
739 on content supplied by the attacker.
741 2. Exim now supports loading some lookup types at run-time, using your
742 platform's dlopen() functionality. This has limited platform support
743 and the intention is not to support every variant, it's limited to
744 dlopen(). This permits the main Exim binary to not be linked against
745 all the libraries needed for all the lookup types.
751 NOTE: this version is not guaranteed backwards-compatible, please read the
752 items below carefully
754 1. A new main configuration option, "openssl_options", is available if Exim
755 is built with SSL support provided by OpenSSL. The option allows
756 administrators to specify OpenSSL options to be used on connections;
757 typically this is to set bug compatibility features which the OpenSSL
758 developers have not enabled by default. There may be security
759 consequences for certain options, so these should not be changed
762 2. A new pipe transport option, "permit_coredumps", may help with problem
763 diagnosis in some scenarios. Note that Exim is typically installed as
764 a setuid binary, which on most OSes will inhibit coredumps by default,
765 so that safety mechanism would have to be overridden for this option to
766 be able to take effect.
768 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
769 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
770 Note that this switches Exim to use a new API ("INSTREAM") and a future
771 release of ClamAV will remove support for the old API ("STREAM").
773 The av_scanner option, when set to "clamd", now takes an optional third
774 part, "local", which causes Exim to pass a filename to ClamAV instead of
775 the file content. This is the same behaviour as when clamd is pointed at
776 a Unix-domain socket. For example:
778 av_scanner = clamd:192.0.2.3 1234:local
780 ClamAV's ExtendedDetectionInfo response format is now handled.
782 4. There is now a -bmalware option, restricted to admin users. This option
783 takes one parameter, a filename, and scans that file with Exim's
784 malware-scanning framework. This is intended purely as a debugging aid
785 to ensure that Exim's scanning is working, not to replace other tools.
786 Note that the ACL framework is not invoked, so if av_scanner references
787 ACL variables without a fallback then this will fail.
789 5. There is a new expansion operator, "reverse_ip", which will reverse IP
790 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
792 ${reverse_ip:192.0.2.4}
794 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
795 -> 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
797 6. There is a new ACL control called "debug", to enable debug logging.
798 This allows selective logging of certain incoming transactions within
799 production environments, with some care. It takes two options, "tag"
800 and "opts"; "tag" is included in the filename of the log and "opts"
801 is used as per the -d<options> command-line option. Examples, which
802 don't all make sense in all contexts:
805 control = debug/tag=.$sender_host_address
806 control = debug/opts=+expand+acl
807 control = debug/tag=.$message_exim_id/opts=+expand
809 7. It has always been implicit in the design and the documentation that
810 "the Exim user" is not root. src/EDITME said that using root was
811 "very strongly discouraged". This is not enough to keep people from
812 shooting themselves in the foot in days when many don't configure Exim
813 themselves but via package build managers. The security consequences of
814 running various bits of network code are severe if there should be bugs in
815 them. As such, the Exim user may no longer be root. If configured
816 statically, Exim will refuse to build. If configured as ref:user then Exim
817 will exit shortly after start-up. If you must shoot yourself in the foot,
818 then henceforth you will have to maintain your own local patches to strip
821 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
822 condition logic to determine truth/failure and will fail to expand many
823 strings, bool_lax{} uses the router condition logic, where most strings
825 Note: bool{00} is false, bool_lax{00} is true.
827 9. Routers now support multiple "condition" tests.
829 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
830 Setting this allows an admin to define which entry in the tcpwrappers
831 config file will be used to control access to the daemon. This option
832 is only available when Exim is built with USE_TCP_WRAPPERS. The
833 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
836 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
837 the Exim run-time user, instead of root.
839 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
840 is forced on. This is mitigated by the new build option
841 TRUSTED_CONFIG_LIST which defines a list of configuration files which
842 are trusted; one per line. If a config file is owned by root and matches
843 a pathname in the list, then it may be invoked by the Exim build-time
844 user without Exim relinquishing root privileges.
846 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
847 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
848 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
849 include the main config. As a transition mechanism, we are temporarily
850 providing a work-around: the new build option WHITELIST_D_MACROS provides
851 a colon-separated list of macro names which may be overridden by the Exim
852 run-time user. The values of these macros are constrained to the regex
853 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
859 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
860 writable, the other to locking of MBX folders (not mbox).
862 2. MySQL stored procedures are now supported.
864 3. The dkim_domain transport option is now a list, not a single string, and
865 messages will be signed for each element in the list (discarding
868 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
869 in the presence of multiple character strings within the RR. Prior to 4.70,
870 only the first string would be returned. The dnsdb lookup now, by default,
871 preserves the pre-4.70 semantics, but also now takes an extended output
872 separator specification. The separator can be followed by a semicolon, to
873 concatenate the individual text strings together with no join character,
874 or by a comma and a second separator character, in which case the text
875 strings within a TXT record are joined on that second character.
876 Administrators are reminded that DNS provides no ordering guarantees
877 between multiple records in an RRset. For example:
879 foo.example. IN TXT "a" "b" "c"
880 foo.example. IN TXT "d" "e" "f"
882 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
883 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
884 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
890 1. Native DKIM support without an external library.
891 (Note that if no action to prevent it is taken, a straight upgrade will
892 result in DKIM verification of all signed incoming emails. See spec
893 for details on conditionally disabling)
895 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
897 3. There is now a bool{} expansion condition which maps certain strings to
898 true/false condition values (most likely of use in conjunction with the
899 and{} expansion operator).
901 4. The $spam_score, $spam_bar and $spam_report variables are now available
904 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
905 options, provided that Exim is invoked by an admin_user.
907 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
908 which increases compatibility with older clients at the cost of decreased
909 security. Don't set this unless you need to support such clients.
911 7. There is a new expansion operator, ${randint:...} which will produce a
912 "random" number less than the supplied integer. This randomness is
913 not guaranteed to be cryptographically strong, but depending upon how
914 Exim was built may be better than the most naive schemes.
916 8. Exim now explicitly ensures that SHA256 is available when linked against
919 9. The transport_filter_timeout option now applies to SMTP transports too.
925 1. Preliminary DKIM support in Experimental.
931 1. The body_linecount and body_zerocount C variables are now exported in the
934 2. When a dnslists lookup succeeds, the key that was looked up is now placed
935 in $dnslist_matched. When the key is an IP address, it is not reversed in
936 this variable (though it is, of course, in the actual lookup). In simple
939 deny dnslists = spamhaus.example
941 the key is also available in another variable (in this case,
942 $sender_host_address). In more complicated cases, however, this is not
943 true. For example, using a data lookup might generate a dnslists lookup
946 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
948 If this condition succeeds, the value in $dnslist_matched might be
949 192.168.6.7 (for example).
951 3. Authenticators now have a client_condition option. When Exim is running as
952 a client, it skips an authenticator whose client_condition expansion yields
953 "0", "no", or "false". This can be used, for example, to skip plain text
954 authenticators when the connection is not encrypted by a setting such as:
956 client_condition = ${if !eq{$tls_cipher}{}}
958 Note that the 4.67 documentation states that $tls_cipher contains the
959 cipher used for incoming messages. In fact, during SMTP delivery, it
960 contains the cipher used for the delivery. The same is true for
963 4. There is now a -Mvc <message-id> option, which outputs a copy of the
964 message to the standard output, in RFC 2822 format. The option can be used
965 only by an admin user.
967 5. There is now a /noupdate option for the ratelimit ACL condition. It
968 computes the rate and checks the limit as normal, but it does not update
969 the saved data. This means that, in relevant ACLs, it is possible to lookup
970 the existence of a specified (or auto-generated) ratelimit key without
971 incrementing the ratelimit counter for that key.
973 In order for this to be useful, another ACL entry must set the rate
974 for the same key somewhere (otherwise it will always be zero).
979 # Read the rate; if it doesn't exist or is below the maximum
981 deny ratelimit = 100 / 5m / strict / noupdate
982 log_message = RATE: $sender_rate / $sender_rate_period \
983 (max $sender_rate_limit)
985 [... some other logic and tests...]
987 warn ratelimit = 100 / 5m / strict / per_cmd
988 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
989 (max $sender_rate_limit)
990 condition = ${if le{$sender_rate}{$sender_rate_limit}}
994 6. The variable $max_received_linelength contains the number of bytes in the
995 longest line that was received as part of the message, not counting the
996 line termination character(s).
998 7. Host lists can now include +ignore_defer and +include_defer, analogous to
999 +ignore_unknown and +include_unknown. These options should be used with
1000 care, probably only in non-critical host lists such as whitelists.
1002 8. There's a new option called queue_only_load_latch, which defaults true.
1003 If set false when queue_only_load is greater than zero, Exim re-evaluates
1004 the load for each incoming message in an SMTP session. Otherwise, once one
1005 message is queued, the remainder are also.
1007 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
1008 cases when an SMTP session ends without sending QUIT. However, when Exim
1009 itself is is bad trouble, such as being unable to write to its log files,
1010 this ACL is not run, because it might try to do things (such as write to
1011 log files) that make the situation even worse.
1013 Like the QUIT ACL, this new ACL is provided to make it possible to gather
1014 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
1015 modifier is forbidden in this ACL.
1017 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
1018 to a string that indicates the reason for the termination of the SMTP
1019 connection. The possible values are:
1021 acl-drop Another ACL issued a "drop" command
1022 bad-commands Too many unknown or non-mail commands
1023 command-timeout Timeout while reading SMTP commands
1024 connection-lost The SMTP connection has been lost
1025 data-timeout Timeout while reading message data
1026 local-scan-error The local_scan() function crashed
1027 local-scan-timeout The local_scan() function timed out
1028 signal-exit SIGTERM or SIGINT
1029 synchronization-error SMTP synchronization error
1030 tls-failed TLS failed to start
1032 In most cases when an SMTP connection is closed without having received
1033 QUIT, Exim sends an SMTP response message before actually closing the
1034 connection. With the exception of acl-drop, the default message can be
1035 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
1036 "drop" verb in another ACL, it is the message from the other ACL that is
1039 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
1040 servers with individual queries. This is done by starting the query with
1041 "servers=x:y:z;", where each item in the list may take one of two forms:
1043 (1) If it is just a host name, the appropriate global option (mysql_servers
1044 or pgsql_servers) is searched for a host of the same name, and the
1045 remaining parameters (database, user, password) are taken from there.
1047 (2) If it contains any slashes, it is taken as a complete parameter set.
1049 The list of servers is used in exactly the same was as the global list.
1050 Once a connection to a server has happened and a query has been
1051 successfully executed, processing of the lookup ceases.
1053 This feature is intended for use in master/slave situations where updates
1054 are occurring, and one wants to update a master rather than a slave. If the
1055 masters are in the list for reading, you might have:
1057 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1059 In an updating lookup, you could then write
1061 ${lookup mysql{servers=master; UPDATE ...}
1063 If, on the other hand, the master is not to be used for reading lookups:
1065 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1067 you can still update the master by
1069 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1071 11. The message_body_newlines option (default FALSE, for backwards
1072 compatibility) can be used to control whether newlines are present in
1073 $message_body and $message_body_end. If it is FALSE, they are replaced by
1080 1. There is a new log selector called smtp_no_mail, which is not included in
1081 the default setting. When it is set, a line is written to the main log
1082 whenever an accepted SMTP connection terminates without having issued a
1085 2. When an item in a dnslists list is followed by = and & and a list of IP
1086 addresses, the behaviour was not clear when the lookup returned more than
1087 one IP address. This has been solved by the addition of == and =& for "all"
1088 rather than the default "any" matching.
1090 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1091 for the cipher algorithms. New options have been added to allow some of the
1092 other parameters to be varied.
1094 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1095 set, Exim compiles a runtime option called disable_fsync.
1097 5. There is a new variable called $smtp_count_at_connection_start.
1099 6. There's a new control called no_pipelining.
1101 7. There are two new variables called $sending_ip_address and $sending_port.
1102 These are set whenever an SMTP connection to another host has been set up.
1104 8. The expansion of the helo_data option in the smtp transport now happens
1105 after the connection to the server has been made.
1107 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1108 are encoded as per RFC 2047.
1110 10. There is a new log selector called "pid", which causes the current process
1111 id to be added to every log line, in square brackets, immediately after the
1114 11. Exim has been modified so that it flushes SMTP output before implementing
1115 a delay in an ACL. It also flushes the output before performing a callout,
1116 as this can take a substantial time. These behaviours can be disabled by
1117 obeying control = no_delay_flush or control = no_callout_flush,
1118 respectively, at some earlier stage of the connection.
1120 12. There are two new expansion conditions that iterate over a list. They are
1121 called forany and forall.
1123 13. There's a new global option called dsn_from that can be used to vary the
1124 contents of From: lines in bounces and other automatically generated
1125 messages ("delivery status notifications" - hence the name of the option).
1127 14. The smtp transport has a new option called hosts_avoid_pipelining.
1129 15. By default, exigrep does case-insensitive matches. There is now a -I option
1130 that makes it case-sensitive.
1132 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1133 been added to string expansions to make it easier to process lists of
1134 items, typically addresses.
1136 17. There's a new ACL modifier called "continue". It does nothing of itself,
1137 and processing of the ACL always continues with the next condition or
1138 modifier. It is provided so that the side effects of expanding its argument
1141 18. It is now possible to use newline and other control characters (those with
1142 values less than 32, plus DEL) as separators in lists.
1144 19. The exigrep utility now has a -v option, which inverts the matching
1147 20. The host_find_failed option in the manualroute router can now be set to
1154 No new features were added to 4.66.
1160 No new features were added to 4.65.
1166 1. ACL variables can now be given arbitrary names, as long as they start with
1167 "acl_c" or "acl_m" (for connection variables and message variables), are at
1168 least six characters long, with the sixth character being either a digit or
1171 2. There is a new ACL modifier called log_reject_target. It makes it possible
1172 to specify which logs are used for messages about ACL rejections.
1174 3. There is a new authenticator called "dovecot". This is an interface to the
1175 authentication facility of the Dovecot POP/IMAP server, which can support a
1176 number of authentication methods.
1178 4. The variable $message_headers_raw provides a concatenation of all the
1179 messages's headers without any decoding. This is in contrast to
1180 $message_headers, which does RFC2047 decoding on the header contents.
1182 5. In a DNS black list, if two domain names, comma-separated, are given, the
1183 second is used first to do an initial check, making use of any IP value
1184 restrictions that are set. If there is a match, the first domain is used,
1185 without any IP value restrictions, to get the TXT record.
1187 6. All authenticators now have a server_condition option.
1189 7. There is a new command-line option called -Mset. It is useful only in
1190 conjunction with -be (that is, when testing string expansions). It must be
1191 followed by a message id; Exim loads the given message from its spool
1192 before doing the expansions.
1194 8. Another similar new command-line option is called -bem. It operates like
1195 -be except that it must be followed by the name of a file that contains a
1198 9. When an address is delayed because of a 4xx response to a RCPT command, it
1199 is now the combination of sender and recipient that is delayed in
1200 subsequent queue runs until its retry time is reached.
1202 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1203 shift, have been added to the eval: and eval10: expansion items.
1205 11. The variables $interface_address and $interface_port have been renamed
1206 as $received_ip_address and $received_port, to make it clear that they
1207 relate to message reception rather than delivery. (The old names remain
1208 available for compatibility.)
1210 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1211 to vary the message that is sent when an SMTP command is accepted.
1217 1. There is a new Boolean option called filter_prepend_home for the redirect
1220 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1221 start of receiving a non-SMTP message, before any of the message has been
1224 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1225 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1226 start of the message for an SMTP error code.
1228 4. There is a new parameter for LDAP lookups called "referrals", which takes
1229 one of the settings "follow" (the default) or "nofollow".
1231 5. Version 20070721.2 of exipick now included, offering these new options:
1233 After all other sorting options have bee processed, reverse order
1234 before displaying messages (-R is synonym).
1236 Randomize order of matching messages before displaying.
1238 Instead of displaying the matching messages, display the sum
1240 --sort <variable>[,<variable>...]
1241 Before displaying matching messages, sort the messages according to
1242 each messages value for each variable.
1244 Negate the value for every test (returns inverse output from the
1245 same criteria without --not).
1251 1. The ${readsocket expansion item now supports Internet domain sockets as well
1252 as Unix domain sockets. If the first argument begins "inet:", it must be of
1253 the form "inet:host:port". The port is mandatory; it may be a number or the
1254 name of a TCP port in /etc/services. The host may be a name, or it may be an
1255 IP address. An ip address may optionally be enclosed in square brackets.
1256 This is best for IPv6 addresses. For example:
1258 ${readsocket{inet:[::1]:1234}{<request data>}...
1260 Only a single host name may be given, but if looking it up yield more than
1261 one IP address, they are each tried in turn until a connection is made. Once
1262 a connection has been made, the behaviour is as for ${readsocket with a Unix
1265 2. If a redirect router sets up file or pipe deliveries for more than one
1266 incoming address, and the relevant transport has batch_max set greater than
1267 one, a batch delivery now occurs.
1269 3. The appendfile transport has a new option called maildirfolder_create_regex.
1270 Its value is a regular expression. For a maildir delivery, this is matched
1271 against the maildir directory; if it matches, Exim ensures that a
1272 maildirfolder file is created alongside the new, cur, and tmp directories.
1278 The documentation is up-to-date for the 4.61 release. Major new features since
1279 the 4.60 release are:
1281 . An option called disable_ipv6, to disable the use of IPv6 completely.
1283 . An increase in the number of ACL variables to 20 of each type.
1285 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1286 $2, $3, (though those are still set) because the numeric variables get used
1287 for other things in complicated expansions.
1289 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1291 . It is possible to use setclassresources() on some BSD OS to control the
1292 resources used in pipe deliveries.
1294 . A new ACL modifier called add_header, which can be used with any verb.
1296 . More errors are detectable in retry rules.
1298 There are a number of other additions too.
1304 The documentation is up-to-date for the 4.60 release. Major new features since
1305 the 4.50 release are:
1307 . Support for SQLite.
1309 . Support for IGNOREQUOTA in LMTP.
1311 . Extensions to the "submission mode" features.
1313 . Support for Client SMTP Authorization (CSA).
1315 . Support for ratelimiting hosts and users.
1317 . New expansion items to help with the BATV "prvs" scheme.
1319 . A "match_ip" condition, that matches an IP address against a list.
1321 There are many more minor changes.