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