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