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