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